Context-specific user interfaces

ABSTRACT

Context-specific user interfaces, e.g., for use with a portable multifunction device, provide, inter alia, indications of time and, optionally, a variety of additional information. A user interface screen including a current time indicator and a first platter is displayed. The first platter is at a first position, is associated with a first application, and displays a first set of information obtained from the first application. The first set of information relates to a first temporal context of the current day. In response to detecting a user input, the first platter is displayed at a second position and a second platter is displayed at the first position. The second platter is associated with a second application and displays a second set of information obtained from the second application. The second set of information relates to a second temporal context of the current day.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.17/087,845, entitled “Context-Specific User Interfaces,” filed Nov. 3,2020, which is a continuation of U.S. patent application Ser. No.15/798,235, now U.S. Pat. No. 10,838,586, entitled “Context-SpecificUser Interfaces,” filed Oct. 30, 2017, which claims priority to U.S.Provisional Patent Application Ser. No. 62/505,782, entitled“Context-Specific User Interfaces,” filed May 12, 2017, the contents ofeach of which are hereby incorporated by reference in their entirety.

This application relates to the following applications: InternationalPatent Application Serial No. PCT/US2015/034604, titled“Context-Specific User Interfaces,” filed Jun. 7, 2015, published asWIPO Publication No. WO/2016/022203; International Patent ApplicationSerial No. PCT/US2015/034606, titled “Context-Specific User Interfaces,”filed Jun. 7, 2015, published as WIPO Publication No. WO/2016/022204;and International Patent Application Serial No. PCT/US2015/034607,titled “Context-Specific User Interfaces,” filed Jun. 7, 2015, publishedas WIPO Publication No. WO/2016/022205. The content of theseapplications is hereby incorporated by reference in their entirety.

FIELD

The present disclosure relates generally to computer user interfaces,and more specifically to techniques for providing context-specific userinterfaces.

BACKGROUND

Portable multifunction devices allow users to access information from avariety of applications and data sources on a reduced-size device theycan keep with them throughout the day in a variety of contexts (e.g., atwork, at home, while traveling, etc.). However, as context changes, thetypes of information a user may wish to view can also change. Thus, itis a challenge to provide an efficient interface that displays relevantinformation to a user throughout the day. For example, a user may wishto know the time of sunset, but a widget dedicated to sunset time isonly relevant to a user as sunset approaches. The rest of the day, thisscreen “real estate” is providing irrelevant information and taking upspace that could be used to provide more relevant information. This is aparticular concern for portable devices with reduced-size interfaces.

SUMMARY

Users rely on portable multifunction devices for keeping time, among avariety of other operations including running software applications.However, some techniques for providing context-specific user interfaces(e.g., for keeping time and/or other operations) are generallycumbersome and inefficient. For example, some existing techniques use acomplex and time-consuming user interface, which may include multiplekey presses or keystrokes. Some existing techniques require moremultiple user interactions in order to display all of the informationthe user wishes to view. Existing techniques require more time thannecessary, wasting user time and device energy. This latterconsideration is particularly important in battery-operated devices.

Accordingly, the present technique provides electronic devices withfaster, more efficient methods and interfaces for providingcontext-specific user interfaces. Such methods and interfaces optionallycomplement or replace other methods for providing context-specific userinterfaces. Such methods and interfaces reduce the cognitive burden on auser and produce a more efficient human-machine interface. Forbattery-operated computing devices, such methods and interfaces conservepower and increase the time between battery charges and reduce thenumber of unnecessary, extraneous, and/or repetitive received inputsrequired to access information.

In some embodiments, a method comprises at an electronic device with adisplay, one or more processors, and memory: displaying on the display auser interface screen comprising: a current time indicator; and a firstplatter at a first position on the display, wherein the first platter isassociated with a first application and displays a first set ofinformation obtained from the first application, wherein the first setof information relates to a first temporal context of the current day;detecting a user input; and in response to detecting the user input:displaying the first platter at a second position different from thefirst position on the display; and displaying a second platter at thefirst position on the display, wherein the second platter is associatedwith a second application and displays a second set of informationobtained from the second application, wherein the second set ofinformation relates to a second temporal context of the current day, andwherein the first and the second applications are different.

In some embodiments, a method comprises at an electronic device with adisplay, one or more processors, and memory: at a first time of thecurrent day, displaying on the display a first user interface screencomprising: a current time indicator, wherein the current time indicatorreflects the first time of the current day; a first platter at a firstposition on the display, wherein the first platter is associated with afirst application and displays a first set of information obtained fromthe first application, wherein the first set of information relates to afirst temporal context of the current day; and an affordance at a secondposition on the display, wherein the affordance represents anapplication; detecting a first user input corresponding to a request toscroll the first user interface screen; and in response to detecting thefirst user input: maintaining display of the affordance at the secondposition; and displaying a second platter at the first position, whereinthe second platter is associated with a second application and displaysa second set of information obtained from the second application, andwherein the second set of information relates to the current day; at asecond time of the current day different from the first time, displayingon the display a second user interface screen comprising: the currenttime indicator, wherein the current time indicator reflects the secondtime of the current day; a third platter at the first position on thedisplay, wherein the third platter is associated with a thirdapplication and displays a third set of information obtained from thethird application, wherein the third set of information relates to athird temporal context of the current day; and the affordance at thesecond position on the display; detecting a second user inputcorresponding to a request to scroll the second user interface screen;and in response to detecting the second user input: maintaining displayof the affordance at the second position; and displaying the secondplatter at the first position.

In some embodiments, a method comprises at an electronic device with adisplay, one or more processors, and memory: displaying on the display auser interface screen comprising: a current time indicator; and a firstnon-textual, graphical depiction of a first set of information obtainedfrom a first application, wherein the first set of information relatesto a first temporal context of the current day; detecting a user input;and in response to detecting the user input: ceasing to display thefirst non-textual, graphical depiction; and displaying a secondnon-textual, graphical depiction, wherein the second non-textual,graphical depiction depicts a second set of information obtained from asecond application, wherein the second set of information relates to asecond temporal context of the current day, and wherein the first andthe second applications are different.

In some embodiments, a method comprises at an electronic device with adisplay, one or more processors, and memory: displaying on the display auser interface screen comprising: a current time indicator; and abackground; detecting a change in time; in response to detecting thechange in time: selecting a first portion of an image, wherein the firstportion is less than the entire image; reflecting the first portionacross a first plurality of axes of reflection to generate a firstplurality of reflected portions; and replacing the background with afirst composite image comprising the first plurality of reflectedportions; detecting a second change in time; and in response todetecting the second change in time: selecting a second portion of theimage, wherein the second portion is less than the entire image, andwherein the second portion is different from the first portion;reflecting the second portion across a second plurality of axes ofreflection to generate a second plurality of reflected portions; andreplacing the first composite image with a second composite imagecomprising the second plurality of reflected portions.

In some embodiments, a method comprises at an electronic device with adisplay, one or more processors, and memory: displaying on the display auser interface screen comprising: a current time indicator; and a firstcomposite image that is generated by the electronic device by: selectinga first portion of an image; reflecting the first portion across a firstplurality of axes of reflection to generate a first plurality ofreflected portions; and displaying the first plurality of reflectedportions; detecting a user input corresponding to a request to edit thefirst composite image; and in response to detecting the user input,ceasing to display the first composite image and displaying a secondcomposite image that is generated by the electronic device by: selectinga second portion of the image; reflecting the second portion across asecond plurality of axes of reflection to generate a second plurality ofreflected portions, wherein the first and the second plurality of axesof reflection are different; and displaying the second plurality ofreflected portions.

In some embodiments, a non-transitory computer-readable storage mediumstores one or more programs configured to be executed by one or moreprocessors of an electronic device with a display, the one or moreprograms including instructions for: displaying on the display a userinterface screen comprising: a current time indicator; and a firstplatter at a first position on the display, wherein the first platter isassociated with a first application and displays a first set ofinformation obtained from the first application, wherein the first setof information relates to a first temporal context of the current day;detecting a user input; and in response to detecting the user input:displaying the first platter at a second position different from thefirst position on the display; and displaying a second platter at thefirst position on the display, wherein the second platter is associatedwith a second application and displays a second set of informationobtained from the second application, wherein the second set ofinformation relates to a second temporal context of the current day, andwherein the first and the second applications are different.

In some embodiments, a non-transitory computer-readable storage mediumstores one or more programs configured to be executed by one or moreprocessors of an electronic device with a display, the one or moreprograms including instructions for: at a first time of the current day,displaying on the display a first user interface screen comprising: acurrent time indicator, wherein the current time indicator reflects thefirst time of the current day; a first platter at a first position onthe display, wherein the first platter is associated with a firstapplication and displays a first set of information obtained from thefirst application, wherein the first set of information relates to afirst temporal context of the current day; and an affordance at a secondposition on the display, wherein the affordance represents anapplication; detecting a first user input corresponding to a request toscroll the first user interface screen; and in response to detecting thefirst user input: maintaining display of the affordance at the secondposition; and displaying a second platter at the first position, whereinthe second platter is associated with a second application and displaysa second set of information obtained from the second application, andwherein the second set of information relates to the current day; at asecond time of the current day different from the first time, displayingon the display a second user interface screen comprising: the currenttime indicator, wherein the current time indicator reflects the secondtime of the current day; a third platter at the first position on thedisplay, wherein the third platter is associated with a thirdapplication and displays a third set of information obtained from thethird application, wherein the third set of information relates to athird temporal context of the current day; and the affordance at thesecond position on the display; detecting a second user inputcorresponding to a request to scroll the second user interface screen;and in response to detecting the second user input: maintaining displayof the affordance at the second position; and displaying the secondplatter at the first position.

In some embodiments, a non-transitory computer-readable storage mediumstores one or more programs configured to be executed by one or moreprocessors of an electronic device with a display, the one or moreprograms including instructions for: displaying on the display a userinterface screen comprising: a current time indicator; and a firstnon-textual, graphical depiction of a first set of information obtainedfrom a first application, wherein the first set of information relatesto a first temporal context of the current day; detecting a user input;and in response to detecting the user input: ceasing to display thefirst non-textual, graphical depiction; and displaying a secondnon-textual, graphical depiction, wherein the second non-textual,graphical depiction depicts a second set of information obtained from asecond application, wherein the second set of information relates to asecond temporal context of the current day, and wherein the first andthe second applications are different.

In some embodiments, a non-transitory computer-readable storage mediumstores one or more programs configured to be executed by one or moreprocessors of an electronic device with a display, the one or moreprograms including instructions for: displaying on the display a userinterface screen comprising: a current time indicator; and a background;detecting a change in time; in response to detecting the change in time:selecting a first portion of an image, wherein the first portion is lessthan the entire image; reflecting the first portion across a firstplurality of axes of reflection to generate a first plurality ofreflected portions; and replacing the background with a first compositeimage comprising the first plurality of reflected portions; detecting asecond change in time; and in response to detecting the second change intime: selecting a second portion of the image, wherein the secondportion is less than the entire image, and wherein the second portion isdifferent from the first portion; reflecting the second portion across asecond plurality of axes of reflection to generate a second plurality ofreflected portions; and replacing the first composite image with asecond composite image comprising the second plurality of reflectedportions.

In some embodiments, a non-transitory computer-readable storage mediumstores one or more programs configured to be executed by one or moreprocessors of an electronic device with a display, the one or moreprograms including instructions for: displaying on the display a userinterface screen comprising: a current time indicator; and a firstcomposite image that is generated by the electronic device by: selectinga first portion of an image; reflecting the first portion across a firstplurality of axes of reflection to generate a first plurality ofreflected portions; and displaying the first plurality of reflectedportions; detecting a user input corresponding to a request to edit thefirst composite image; and in response to detecting the user input,ceasing to display the first composite image and displaying a secondcomposite image that is generated by the electronic device by: selectinga second portion of the image; reflecting the second portion across asecond plurality of axes of reflection to generate a second plurality ofreflected portions, wherein the first and the second plurality of axesof reflection are different; and displaying the second plurality ofreflected portions.

In some embodiments, a transitory computer-readable storage mediumstores one or more programs configured to be executed by one or moreprocessors of an electronic device with a display, the one or moreprograms including instructions for: displaying on the display a userinterface screen comprising: a current time indicator; and a firstplatter at a first position on the display, wherein the first platter isassociated with a first application and displays a first set ofinformation obtained from the first application, wherein the first setof information relates to a first temporal context of the current day;detecting a user input; and in response to detecting the user input:displaying the first platter at a second position different from thefirst position on the display; and displaying a second platter at thefirst position on the display, wherein the second platter is associatedwith a second application and displays a second set of informationobtained from the second application, wherein the second set ofinformation relates to a second temporal context of the current day, andwherein the first and the second applications are different.

In some embodiments, a transitory computer-readable storage mediumstores one or more programs configured to be executed by one or moreprocessors of an electronic device with a display, the one or moreprograms including instructions for: at a first time of the current day,displaying on the display a first user interface screen comprising: acurrent time indicator, wherein the current time indicator reflects thefirst time of the current day; a first platter at a first position onthe display, wherein the first platter is associated with a firstapplication and displays a first set of information obtained from thefirst application, wherein the first set of information relates to afirst temporal context of the current day; and an affordance at a secondposition on the display, wherein the affordance represents anapplication; detecting a first user input corresponding to a request toscroll the first user interface screen; and in response to detecting thefirst user input: maintaining display of the affordance at the secondposition; and displaying a second platter at the first position, whereinthe second platter is associated with a second application and displaysa second set of information obtained from the second application, andwherein the second set of information relates to the current day; at asecond time of the current day different from the first time, displayingon the display a second user interface screen comprising: the currenttime indicator, wherein the current time indicator reflects the secondtime of the current day; a third platter at the first position on thedisplay, wherein the third platter is associated with a thirdapplication and displays a third set of information obtained from thethird application, wherein the third set of information relates to athird temporal context of the current day; and the affordance at thesecond position on the display; detecting a second user inputcorresponding to a request to scroll the second user interface screen;and in response to detecting the second user input: maintaining displayof the affordance at the second position; and displaying the secondplatter at the first position.

In some embodiments, a transitory computer-readable storage mediumstores one or more programs configured to be executed by one or moreprocessors of an electronic device with a display, the one or moreprograms including instructions for: displaying on the display a userinterface screen comprising: a current time indicator; and a firstnon-textual, graphical depiction of a first set of information obtainedfrom a first application, wherein the first set of information relatesto a first temporal context of the current day; detecting a user input;and in response to detecting the user input: ceasing to display thefirst non-textual, graphical depiction; and displaying a secondnon-textual, graphical depiction, wherein the second non-textual,graphical depiction depicts a second set of information obtained from asecond application, wherein the second set of information relates to asecond temporal context of the current day, and wherein the first andthe second applications are different.

In some embodiments, a transitory computer-readable storage mediumstores one or more programs configured to be executed by one or moreprocessors of an electronic device with a display, the one or moreprograms including instructions for: displaying on the display a userinterface screen comprising: a current time indicator; and a background;detecting a change in time; in response to detecting the change in time:selecting a first portion of an image, wherein the first portion is lessthan the entire image; reflecting the first portion across a firstplurality of axes of reflection to generate a first plurality ofreflected portions; and replacing the background with a first compositeimage comprising the first plurality of reflected portions; detecting asecond change in time; and in response to detecting the second change intime: selecting a second portion of the image, wherein the secondportion is less than the entire image, and wherein the second portion isdifferent from the first portion; reflecting the second portion across asecond plurality of axes of reflection to generate a second plurality ofreflected portions; and replacing the first composite image with asecond composite image comprising the second plurality of reflectedportions.

In some embodiments, a transitory computer-readable storage mediumstores one or more programs configured to be executed by one or moreprocessors of an electronic device with a display, the one or moreprograms including instructions for: displaying on the display a userinterface screen comprising: a current time indicator; and a firstcomposite image that is generated by the electronic device by: selectinga first portion of an image; reflecting the first portion across a firstplurality of axes of reflection to generate a first plurality ofreflected portions; and displaying the first plurality of reflectedportions; detecting a user input corresponding to a request to edit thefirst composite image; and in response to detecting the user input,ceasing to display the first composite image and displaying a secondcomposite image that is generated by the electronic device by: selectinga second portion of the image; reflecting the second portion across asecond plurality of axes of reflection to generate a second plurality ofreflected portions, wherein the first and the second plurality of axesof reflection are different; and displaying the second plurality ofreflected portions.

In some embodiments, an electronic device comprises a display; one ormore processors; and memory storing one or more programs configured tobe executed by the one or more processors, the one or more programsincluding instructions for: displaying on the display a user interfacescreen comprising: a current time indicator; and a first platter at afirst position on the display, wherein the first platter is associatedwith a first application and displays a first set of informationobtained from the first application, wherein the first set ofinformation relates to a first temporal context of the current day;detecting a user input; and in response to detecting the user input:displaying the first platter at a second position different from thefirst position on the display; and displaying a second platter at thefirst position on the display, wherein the second platter is associatedwith a second application and displays a second set of informationobtained from the second application, wherein the second set ofinformation relates to a second temporal context of the current day, andwherein the first and the second applications are different.

In some embodiments, an electronic device comprises a display; one ormore processors; and memory storing one or more programs configured tobe executed by the one or more processors, the one or more programsincluding instructions for: at a first time of the current day,displaying on the display a first user interface screen comprising: acurrent time indicator, wherein the current time indicator reflects thefirst time of the current day; a first platter at a first position onthe display, wherein the first platter is associated with a firstapplication and displays a first set of information obtained from thefirst application, wherein the first set of information relates to afirst temporal context of the current day; and an affordance at a secondposition on the display, wherein the affordance represents anapplication; detecting a first user input corresponding to a request toscroll the first user interface screen; and in response to detecting thefirst user input: maintaining display of the affordance at the secondposition; and displaying a second platter at the first position, whereinthe second platter is associated with a second application and displaysa second set of information obtained from the second application, andwherein the second set of information relates to the current day; at asecond time of the current day different from the first time, displayingon the display a second user interface screen comprising: the currenttime indicator, wherein the current time indicator reflects the secondtime of the current day; a third platter at the first position on thedisplay, wherein the third platter is associated with a thirdapplication and displays a third set of information obtained from thethird application, wherein the third set of information relates to athird temporal context of the current day; and the affordance at thesecond position on the display; detecting a second user inputcorresponding to a request to scroll the second user interface screen;and in response to detecting the second user input: maintaining displayof the affordance at the second position; and displaying the secondplatter at the first position.

In some embodiments, an electronic device comprises a display; one ormore processors; and memory storing one or more programs configured tobe executed by the one or more processors, the one or more programsincluding instructions for: displaying on the display a user interfacescreen comprising: a current time indicator; and a first non-textual,graphical depiction of a first set of information obtained from a firstapplication, wherein the first set of information relates to a firsttemporal context of the current day; detecting a user input; and inresponse to detecting the user input: ceasing to display the firstnon-textual, graphical depiction; and displaying a second non-textual,graphical depiction, wherein the second non-textual, graphical depictiondepicts a second set of information obtained from a second application,wherein the second set of information relates to a second temporalcontext of the current day, and wherein the first and the secondapplications are different.

In some embodiments, an electronic device comprises a display; one ormore processors; and memory storing one or more programs configured tobe executed by the one or more processors, the one or more programsincluding instructions for: displaying on the display a user interfacescreen comprising: a current time indicator; and a background; detectinga change in time; in response to detecting the change in time: selectinga first portion of an image, wherein the first portion is less than theentire image; reflecting the first portion across a first plurality ofaxes of reflection to generate a first plurality of reflected portions;and replacing the background with a first composite image comprising thefirst plurality of reflected portions; detecting a second change intime; and in response to detecting the second change in time: selectinga second portion of the image, wherein the second portion is less thanthe entire image, and wherein the second portion is different from thefirst portion; reflecting the second portion across a second pluralityof axes of reflection to generate a second plurality of reflectedportions; and replacing the first composite image with a secondcomposite image comprising the second plurality of reflected portions.

In some embodiments, an electronic device comprises a display; one ormore processors; and memory storing one or more programs configured tobe executed by the one or more processors, the one or more programsincluding instructions for: displaying on the display a user interfacescreen comprising: a current time indicator; and a first composite imagethat is generated by the electronic device by: selecting a first portionof an image; reflecting the first portion across a first plurality ofaxes of reflection to generate a first plurality of reflected portions;and displaying the first plurality of reflected portions; detecting auser input corresponding to a request to edit the first composite image;and in response to detecting the user input, ceasing to display thefirst composite image and displaying a second composite image that isgenerated by the electronic device by: selecting a second portion of theimage; reflecting the second portion across a second plurality of axesof reflection to generate a second plurality of reflected portions,wherein the first and the second plurality of axes of reflection aredifferent; and displaying the second plurality of reflected portions.

In some embodiments, an electronic device comprises a display; means fordisplaying on the display a user interface screen comprising: a currenttime indicator; and a first platter at a first position on the display,wherein the first platter is associated with a first application anddisplays a first set of information obtained from the first application,wherein the first set of information relates to a first temporal contextof the current day; means for detecting a user input; and meansresponsive at least in part to detecting the user input for displayingthe first platter at a second position different from the first positionon the display; and means responsive at least in part to detecting theuser input for displaying a second platter at the first position on thedisplay, wherein the second platter is associated with a secondapplication and displays a second set of information obtained from thesecond application, wherein the second set of information relates to asecond temporal context of the current day, and wherein the first andthe second applications are different.

In some embodiments, an electronic device comprises a display; means fordisplaying on the display, at a first time of the current day, a firstuser interface screen comprising: a current time indicator, wherein thecurrent time indicator reflects the first time of the current day; afirst platter at a first position on the display, wherein the firstplatter is associated with a first application and displays a first setof information obtained from the first application, wherein the firstset of information relates to a first temporal context of the currentday; and an affordance at a second position on the display, wherein theaffordance represents an application; means for detecting a first userinput corresponding to a request to scroll the first user interfacescreen; and means responsive at least in part to detecting the firstuser input for maintaining display of the affordance at the secondposition; and means responsive at least in part to detecting the firstuser input for displaying a second platter at the first position,wherein the second platter is associated with a second application anddisplays a second set of information obtained from the secondapplication, and wherein the second set of information relates to thecurrent day; means for displaying on the display, at a second time ofthe current day different from the first time, a second user interfacescreen comprising: the current time indicator, wherein the current timeindicator reflects the second time of the current day; a third platterat the first position on the display, wherein the third platter isassociated with a third application and displays a third set ofinformation obtained from the third application, wherein the third setof information relates to a third temporal context of the current day;and the affordance at the second position on the display; means fordetecting a second user input corresponding to a request to scroll thesecond user interface screen; and means responsive at least in part todetecting the second user input for maintaining display of theaffordance at the second position; and means responsive at least in partto detecting the second user input for displaying the second platter atthe first position.

In some embodiments, an electronic device comprises a display; means fordisplaying on the display a user interface screen comprising: a currenttime indicator; and a first non-textual, graphical depiction of a firstset of information obtained from a first application, wherein the firstset of information relates to a first temporal context of the currentday; means for detecting a user input; and means responsive at least inpart to detecting the user input for ceasing to display the firstnon-textual, graphical depiction; and means responsive at least in partto detecting the user input for displaying a second non-textual,graphical depiction, wherein the second non-textual, graphical depictiondepicts a second set of information obtained from a second application,wherein the second set of information relates to a second temporalcontext of the current day, and wherein the first and the secondapplications are different.

In some embodiments, an electronic device comprises a display; means fordisplaying on the display a user interface screen comprising: a currenttime indicator; and a background; means for detecting a change in time;means responsive at least in part to detecting the change in time forselecting a first portion of an image, wherein the first portion is lessthan the entire image; means responsive at least in part to detectingthe change in time for reflecting the first portion across a firstplurality of axes of reflection to generate a first plurality ofreflected portions; and means responsive at least in part to detectingthe change in time for replacing the background with a first compositeimage comprising the first plurality of reflected portions; meansdetecting a second change in time; and means responsive at least in partto detecting the second change in time for selecting a second portion ofthe image, wherein the second portion is less than the entire image, andwherein the second portion is different from the first portion; meansresponsive at least in part to detecting the second change in time forreflecting the second portion across a second plurality of axes ofreflection to generate a second plurality of reflected portions; andmeans responsive at least in part to detecting the second change in timefor replacing the first composite image with a second composite imagecomprising the second plurality of reflected portions.

In some embodiments, an electronic device comprises a display; means fordisplaying on the display a user interface screen comprising: a currenttime indicator; and a first composite image that is generated by theelectronic device by: selecting a first portion of an image; reflectingthe first portion across a first plurality of axes of reflection togenerate a first plurality of reflected portions; and displaying thefirst plurality of reflected portions; means for detecting a user inputcorresponding to a request to edit the first composite image; and meansresponsive at least in part to detecting the user input for ceasing todisplay the first composite image and displaying a second compositeimage that is generated by the electronic device by: selecting a secondportion of the image; reflecting the second portion across a secondplurality of axes of reflection to generate a second plurality ofreflected portions, wherein the first and the second plurality of axesof reflection are different; and displaying the second plurality ofreflected portions.

Executable instructions for performing these functions are, optionally,included in a non-transitory computer-readable storage medium or othercomputer program product configured for execution by one or moreprocessors. Executable instructions for performing these functions are,optionally, included in a transitory computer-readable storage medium orother computer program product configured for execution by one or moreprocessors.

Thus, devices are provided with faster, more efficient methods andinterfaces for providing context-specific user interfaces. Such methodsand interfaces may complement or replace other methods for providingcontext-specific user interfaces.

DESCRIPTION OF THE FIGURES

For a better understanding of the various described embodiments,reference should be made to the Description of Embodiments below, inconjunction with the following drawings in which like reference numeralsrefer to corresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having a touch screenin accordance with some embodiments.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on a portable multifunction device in accordance with someembodiments.

FIG. 4B illustrates an exemplary user interface for a multifunctiondevice with a touch-sensitive surface that is separate from the displayin accordance with some embodiments.

FIG. 5A illustrates a personal electronic device in accordance with someembodiments.

FIG. 5B is a block diagram illustrating a personal electronic device inaccordance with some embodiments.

FIGS. 5C-5D illustrate exemplary components of a personal electronicdevice having a touch-sensitive display and intensity sensors inaccordance with some embodiments.

FIGS. 5E-5H illustrate exemplary components and user interfaces of apersonal electronic device in accordance with some embodiments.

FIGS. 6A-6V illustrate exemplary context-specific user interfaces.

FIGS. 7A-7E illustrate a flow diagram depicting a process for providingcontext-specific user interfaces in accordance with some embodiments.

FIGS. 8A-8G illustrate a flow diagram depicting a process for providingcontext-specific user interfaces in accordance with some embodiments.

FIGS. 9A-9L illustrate exemplary context-specific user interfaces.

FIGS. 10A-10C illustrate a flow diagram depicting a process forproviding context-specific user interfaces in accordance with someembodiments.

FIGS. 11A-11N illustrate exemplary context-specific user interfaces.

FIG. 12 illustrates exemplary personal electronic devices.

FIG. 13 illustrates exemplary context-specific user interfaces.

FIGS. 14A-14E illustrate exemplary context-specific user interfaces.

FIGS. 15A-15E illustrate a flow diagram depicting a process forproviding context-specific user interfaces in accordance with someembodiments.

FIGS. 16A-16D illustrate a flow diagram depicting a process forproviding context-specific user interfaces in accordance with someembodiments.

FIGS. 17A & 17B illustrate exemplary techniques for providingcontext-specific user interfaces.

FIG. 18 illustrates a flow diagram depicting a process for providingcontext-specific user interfaces in accordance with some embodiments.

FIGS. 19A-19F illustrate exemplary context-specific user interfaces.

DESCRIPTION OF EMBODIMENTS

The following description sets forth exemplary methods, parameters, andthe like. It should be recognized, however, that such description is notintended as a limitation on the scope of the present disclosure but isinstead provided as a description of exemplary embodiments.

There is a need for electronic devices that provide efficient methodsand interfaces for context-specific user interfaces, e.g., that displaythe time along with additional information. This is particularly truefor portable multifunction devices with reduced-size displays. Providingthe user with relevant information (e.g., obtained from one or moreapplications) at a glance in a convenient, customizable interfacereduces the number of inputs needed to access the information andconserves battery life. Moreover, providing user interfaces that changedisplayed content as the context in which the user is using theinterfaces changes (e.g., throughout the day) makes accessing suchinformation through the interfaces even more efficient. An interfacethat changes the type of displayed information as a user's contextchanges provides more efficient use of screen “real estate,” which inturn reduces the number of user interactions required to access relevantdata at any time of day. Such techniques can reduce the cognitive burdenon a user who uses the context-specific user interfaces to accessinformation and/or keep time. Further, such techniques can reduceprocessor and battery power otherwise wasted on redundant user inputs.

Below, FIGS. 1A-1B, 2, 3, 4A-4B, and 5A-5H provide a description ofexemplary devices for performing the techniques for configuringcontext-specific user interfaces. FIGS. 6A-6V, 9A-9L, 11A-14E, 17A, 17B,and 19A-19F illustrate exemplary user interfaces for providingcontext-specific user interfaces. The user interfaces in the figures arealso used to illustrate the processes described below, including theprocesses in FIGS. 7A-8G, 10A-10C, 15A-16D, and 18 .

Although the following description uses terms “first,” “second,” etc. todescribe various elements, these elements should not be limited by theterms. These terms are only used to distinguish one element fromanother. For example, a first touch could be termed a second touch, and,similarly, a second touch could be termed a first touch, withoutdeparting from the scope of the various described embodiments. The firsttouch and the second touch are both touches, but they are not the sametouch.

The terminology used in the description of the various describedembodiments herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used in thedescription of the various described embodiments and the appendedclaims, the singular forms “a,” “an,” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

The term “if” is, optionally, construed to mean “when” or “upon” or “inresponse to determining” or “in response to detecting,” depending on thecontext. Similarly, the phrase “if it is determined” or “if [a statedcondition or event] is detected” is, optionally, construed to mean “upondetermining” or “in response to determining” or “upon detecting [thestated condition or event]” or “in response to detecting [the statedcondition or event],” depending on the context.

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Exemplary embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, Calif. Other portable electronicdevices, such as laptops or tablet computers with touch-sensitivesurfaces (e.g., touch screen displays and/or touchpads), are,optionally, used. It should also be understood that, in someembodiments, the device is not a portable communications device, but isa desktop computer with a touch-sensitive surface (e.g., a touch screendisplay and/or a touchpad).

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device optionally includes oneor more other physical user-interface devices, such as a physicalkeyboard, a mouse, and/or a joystick.

The device typically supports a variety of applications, such as one ormore of the following: a drawing application, a presentationapplication, a word processing application, a website creationapplication, a disk authoring application, a spreadsheet application, agaming application, a telephone application, a video conferencingapplication, an e-mail application, an instant messaging application, aworkout support application, a photo management application, a digitalcamera application, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that are executed on the device optionally useat least one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the deviceare, optionally, adjusted and/or varied from one application to the nextand/or within a respective application. In this way, a common physicalarchitecture (such as the touch-sensitive surface) of the deviceoptionally supports the variety of applications with user interfacesthat are intuitive and transparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive display system112 in accordance with some embodiments. Touch-sensitive display 112 issometimes called a “touch screen” for convenience and is sometimes knownas or called a “touch-sensitive display system.” Device 100 includesmemory 102 (which optionally includes one or more computer-readablestorage mediums), memory controller 122, one or more processing units(CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry110, speaker 111, microphone 113, input/output (I/O) subsystem 106,other input control devices 116, and external port 124. Device 100optionally includes one or more optical sensors 164. Device 100optionally includes one or more contact intensity sensors 165 fordetecting intensity of contacts on device 100 (e.g., a touch-sensitivesurface such as touch-sensitive display system 112 of device 100).Device 100 optionally includes one or more tactile output generators 167for generating tactile outputs on device 100 (e.g., generating tactileoutputs on a touch-sensitive surface such as touch-sensitive displaysystem 112 of device 100 or touchpad 355 of device 300). Thesecomponents optionally communicate over one or more communication busesor signal lines 103.

As used in the specification and claims, the term “intensity” of acontact on a touch-sensitive surface refers to the force or pressure(force per unit area) of a contact (e.g., a finger contact) on thetouch-sensitive surface, or to a substitute (proxy) for the force orpressure of a contact on the touch-sensitive surface. The intensity of acontact has a range of values that includes at least four distinctvalues and more typically includes hundreds of distinct values (e.g., atleast 256). Intensity of a contact is, optionally, determined (ormeasured) using various approaches and various sensors or combinationsof sensors. For example, one or more force sensors underneath oradjacent to the touch-sensitive surface are, optionally, used to measureforce at various points on the touch-sensitive surface. In someimplementations, force measurements from multiple force sensors arecombined (e.g., a weighted average) to determine an estimated force of acontact. Similarly, a pressure-sensitive tip of a stylus is, optionally,used to determine a pressure of the stylus on the touch-sensitivesurface. Alternatively, the size of the contact area detected on thetouch-sensitive surface and/or changes thereto, the capacitance of thetouch-sensitive surface proximate to the contact and/or changes thereto,and/or the resistance of the touch-sensitive surface proximate to thecontact and/or changes thereto are, optionally, used as a substitute forthe force or pressure of the contact on the touch-sensitive surface. Insome implementations, the substitute measurements for contact force orpressure are used directly to determine whether an intensity thresholdhas been exceeded (e.g., the intensity threshold is described in unitscorresponding to the substitute measurements). In some implementations,the substitute measurements for contact force or pressure are convertedto an estimated force or pressure, and the estimated force or pressureis used to determine whether an intensity threshold has been exceeded(e.g., the intensity threshold is a pressure threshold measured in unitsof pressure). Using the intensity of a contact as an attribute of a userinput allows for user access to additional device functionality that mayotherwise not be accessible by the user on a reduced-size device withlimited real estate for displaying affordances (e.g., on atouch-sensitive display) and/or receiving user input (e.g., via atouch-sensitive display, a touch-sensitive surface, or aphysical/mechanical control such as a knob or a button).

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click” of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as an “down click” or “up click” even when there is no movement ofa physical actuator button associated with the touch-sensitive surfacethat is physically pressed (e.g., displaced) by the user's movements. Asanother example, movement of the touch-sensitive surface is, optionally,interpreted or sensed by the user as “roughness” of the touch-sensitivesurface, even when there is no change in smoothness of thetouch-sensitive surface. While such interpretations of touch by a userwill be subject to the individualized sensory perceptions of the user,there are many sensory perceptions of touch that are common to a largemajority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 1A areimplemented in hardware, software, or a combination of both hardware andsoftware, including one or more signal processing and/orapplication-specific integrated circuits.

Memory 102 optionally includes high-speed random access memory andoptionally also includes non-volatile memory, such as one or moremagnetic disk storage devices, flash memory devices, or othernon-volatile solid-state memory devices. Memory controller 122optionally controls access to memory 102 by other components of device100.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU 120 and memory 102. The one or moreprocessors 120 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data. In some embodiments, peripheralsinterface 118, CPU 120, and memory controller 122 are, optionally,implemented on a single chip, such as chip 104. In some otherembodiments, they are, optionally, implemented on separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The RF circuitry 108optionally includes well-known circuitry for detecting near fieldcommunication (NFC) fields, such as by a short-range communicationradio. The wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies, including but notlimited to Global System for Mobile Communications (GSM), Enhanced DataGSM Environment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity(Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n,and/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, aprotocol for e-mail (e.g., Internet message access protocol (IMAP)and/or post office protocol (POP)), instant messaging (e.g., extensiblemessaging and presence protocol (XMPP), Session Initiation Protocol forInstant Messaging and Presence Leveraging Extensions (SIMPLE), InstantMessaging and Presence Service (IMPS)), and/or Short Message Service(SMS), or any other suitable communication protocol, includingcommunication protocols not yet developed as of the filing date of thisdocument.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data is, optionally,retrieved from and/or transmitted to memory 102 and/or RF circuitry 108by peripherals interface 118. In some embodiments, audio circuitry 110also includes a headset jack (e.g., 212, FIG. 2 ). The headset jackprovides an interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch screen 112 and other input control devices 116, to peripheralsinterface 118. I/O subsystem 106 optionally includes display controller156, optical sensor controller 158, intensity sensor controller 159,haptic feedback controller 161, and one or more input controllers 160for other input or control devices. The one or more input controllers160 receive/send electrical signals from/to other input control devices116. The other input control devices 116 optionally include physicalbuttons (e.g., push buttons, rocker buttons, etc.), dials, sliderswitches, joysticks, click wheels, and so forth. In some alternateembodiments, input controller(s) 160 are, optionally, coupled to any (ornone) of the following: a keyboard, an infrared port, a USB port, and apointer device such as a mouse. The one or more buttons (e.g., 208, FIG.2 ) optionally include an up/down button for volume control of speaker111 and/or microphone 113. The one or more buttons optionally include apush button (e.g., 206, FIG. 2 ).

A quick press of the push button optionally disengages a lock of touchscreen 112 or optionally begins a process that uses gestures on thetouch screen to unlock the device, as described in U.S. patentapplication Ser. No. 11/322,549, “Unlocking a Device by PerformingGestures on an Unlock Image,” filed Dec. 23, 2005, U.S. Pat. No.7,657,849, which is hereby incorporated by reference in its entirety. Alonger press of the push button (e.g., 206) optionally turns power todevice 100 on or off. The functionality of one or more of the buttonsare, optionally, user-customizable. Touch screen 112 is used toimplement virtual or soft buttons and one or more soft keyboards.

Touch-sensitive display 112 provides an input interface and an outputinterface between the device and a user. Display controller 156 receivesand/or sends electrical signals from/to touch screen 112. Touch screen112 displays visual output to the user. The visual output optionallyincludes graphics, text, icons, video, and any combination thereof(collectively termed “graphics”). In some embodiments, some or all ofthe visual output optionally corresponds to user-interface objects.

Touch screen 112 has a touch-sensitive surface, sensor, or set ofsensors that accepts input from the user based on haptic and/or tactilecontact. Touch screen 112 and display controller 156 (along with anyassociated modules and/or sets of instructions in memory 102) detectcontact (and any movement or breaking of the contact) on touch screen112 and convert the detected contact into interaction withuser-interface objects (e.g., one or more soft keys, icons, web pages,or images) that are displayed on touch screen 112. In an exemplaryembodiment, a point of contact between touch screen 112 and the usercorresponds to a finger of the user.

Touch screen 112 optionally uses LCD (liquid crystal display)technology, LPD (light emitting polymer display) technology, or LED(light emitting diode) technology, although other display technologiesare used in other embodiments. Touch screen 112 and display controller156 optionally detect contact and any movement or breaking thereof usingany of a plurality of touch sensing technologies now known or laterdeveloped, including but not limited to capacitive, resistive, infrared,and surface acoustic wave technologies, as well as other proximitysensor arrays or other elements for determining one or more points ofcontact with touch screen 112. In an exemplary embodiment, projectedmutual capacitance sensing technology is used, such as that found in theiPhone® and iPod Touch® from Apple Inc. of Cupertino, Calif.

A touch-sensitive display in some embodiments of touch screen 112 is,optionally, analogous to the multi-touch sensitive touchpads describedin the following U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat.No. 6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932(Westerman), and/or U.S. Patent Publication 2002/0015024A1, each ofwhich is hereby incorporated by reference in its entirety. However,touch screen 112 displays visual output from device 100, whereastouch-sensitive touchpads do not provide visual output.

A touch-sensitive display in some embodiments of touch screen 112 isdescribed in the following applications: (1) U.S. patent applicationSer. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2,2006; (2) U.S. patent application Ser. No. 10/840,862, “MultipointTouchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No.10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30,2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures ForTouch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patentapplication Ser. No. 11/038,590, “Mode-Based Graphical User InterfacesFor Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patentapplication Ser. No. 11/228,758, “Virtual Input Device Placement On ATouch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patentapplication Ser. No. 11/228,700, “Operation Of A Computer With A TouchScreen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser.No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen VirtualKeyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No.11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. Allof these applications are incorporated by reference herein in theirentirety.

Touch screen 112 optionally has a video resolution in excess of 100 dpi.In some embodiments, the touch screen has a video resolution ofapproximately 160 dpi. The user optionally makes contact with touchscreen 112 using any suitable object or appendage, such as a stylus, afinger, and so forth. In some embodiments, the user interface isdesigned to work primarily with finger-based contacts and gestures,which can be less precise than stylus-based input due to the larger areaof contact of a finger on the touch screen. In some embodiments, thedevice translates the rough finger-based input into a precisepointer/cursor position or command for performing the actions desired bythe user.

In some embodiments, in addition to the touch screen, device 100optionally includes a touchpad (not shown) for activating ordeactivating particular functions. In some embodiments, the touchpad isa touch-sensitive area of the device that, unlike the touch screen, doesnot display visual output. The touchpad is, optionally, atouch-sensitive surface that is separate from touch screen 112 or anextension of the touch-sensitive surface formed by the touch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 optionally includes a power managementsystem, one or more power sources (e.g., battery, alternating current(AC)), a recharging system, a power failure detection circuit, a powerconverter or inverter, a power status indicator (e.g., a light-emittingdiode (LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 optionally also includes one or more optical sensors 164.FIG. 1A shows an optical sensor coupled to optical sensor controller 158in I/O subsystem 106. Optical sensor 164 optionally includescharge-coupled device (CCD) or complementary metal-oxide semiconductor(CMOS) phototransistors. Optical sensor 164 receives light from theenvironment, projected through one or more lenses, and converts thelight to data representing an image. In conjunction with imaging module143 (also called a camera module), optical sensor 164 optionallycaptures still images or video. In some embodiments, an optical sensoris located on the back of device 100, opposite touch screen display 112on the front of the device so that the touch screen display is enabledfor use as a viewfinder for still and/or video image acquisition. Insome embodiments, an optical sensor is located on the front of thedevice so that the user's image is, optionally, obtained for videoconferencing while the user views the other video conferenceparticipants on the touch screen display. In some embodiments, theposition of optical sensor 164 can be changed by the user (e.g., byrotating the lens and the sensor in the device housing) so that a singleoptical sensor 164 is used along with the touch screen display for bothvideo conferencing and still and/or video image acquisition.

Device 100 optionally also includes one or more contact intensitysensors 165. FIG. 1A shows a contact intensity sensor coupled tointensity sensor controller 159 in I/O subsystem 106. Contact intensitysensor 165 optionally includes one or more piezoresistive strain gauges,capacitive force sensors, electric force sensors, piezoelectric forcesensors, optical force sensors, capacitive touch-sensitive surfaces, orother intensity sensors (e.g., sensors used to measure the force (orpressure) of a contact on a touch-sensitive surface). Contact intensitysensor 165 receives contact intensity information (e.g., pressureinformation or a proxy for pressure information) from the environment.In some embodiments, at least one contact intensity sensor is collocatedwith, or proximate to, a touch-sensitive surface (e.g., touch-sensitivedisplay system 112). In some embodiments, at least one contact intensitysensor is located on the back of device 100, opposite touch screendisplay 112, which is located on the front of device 100.

Device 100 optionally also includes one or more proximity sensors 166.FIG. 1A shows proximity sensor 166 coupled to peripherals interface 118.Alternately, proximity sensor 166 is, optionally, coupled to inputcontroller 160 in I/O subsystem 106. Proximity sensor 166 optionallyperforms as described in U.S. patent application Ser. No. 11/241,839,“Proximity Detector In Handheld Device”; Ser. No. 11/240,788, “ProximityDetector In Handheld Device”; Ser. No. 11/620,702, “Using Ambient LightSensor To Augment Proximity Sensor Output”; Ser. No. 11/586,862,“Automated Response To And Sensing Of User Activity In PortableDevices”; and Ser. No. 11/638,251, “Methods And Systems For AutomaticConfiguration Of Peripherals,” which are hereby incorporated byreference in their entirety. In some embodiments, the proximity sensorturns off and disables touch screen 112 when the multifunction device isplaced near the user's ear (e.g., when the user is making a phone call).

Device 100 optionally also includes one or more tactile outputgenerators 167. FIG. 1A shows a tactile output generator coupled tohaptic feedback controller 161 in I/O subsystem 106. Tactile outputgenerator 167 optionally includes one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). Contact intensity sensor 165 receives tactile feedbackgeneration instructions from haptic feedback module 133 and generatestactile outputs on device 100 that are capable of being sensed by a userof device 100. In some embodiments, at least one tactile outputgenerator is collocated with, or proximate to, a touch-sensitive surface(e.g., touch-sensitive display system 112) and, optionally, generates atactile output by moving the touch-sensitive surface vertically (e.g.,in/out of a surface of device 100) or laterally (e.g., back and forth inthe same plane as a surface of device 100). In some embodiments, atleast one tactile output generator sensor is located on the back ofdevice 100, opposite touch screen display 112, which is located on thefront of device 100.

Device 100 optionally also includes one or more accelerometers 168. FIG.1A shows accelerometer 168 coupled to peripherals interface 118.Alternately, accelerometer 168 is, optionally, coupled to an inputcontroller 160 in I/O subsystem 106. Accelerometer 168 optionallyperforms as described in U.S. Patent Publication No. 20050190059,“Acceleration-based Theft Detection System for Portable ElectronicDevices,” and U.S. Patent Publication No. 20060017692, “Methods AndApparatuses For Operating A Portable Device Based On An Accelerometer,”both of which are incorporated by reference herein in their entirety. Insome embodiments, information is displayed on the touch screen displayin a portrait view or a landscape view based on an analysis of datareceived from the one or more accelerometers. Device 100 optionallyincludes, in addition to accelerometer(s) 168, a magnetometer (notshown) and a GPS (or GLONASS or other global navigation system) receiver(not shown) for obtaining information concerning the location andorientation (e.g., portrait or landscape) of device 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,graphics module (or set of instructions) 132, text input module (or setof instructions) 134, Global Positioning System (GPS) module (or set ofinstructions) 135, and applications (or sets of instructions) 136.Furthermore, in some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3 )stores device/global internal state 157, as shown in FIGS. 1A and 3 .Device/global internal state 157 includes one or more of: activeapplication state, indicating which applications, if any, are currentlyactive; display state, indicating what applications, views or otherinformation occupy various regions of touch screen display 112; sensorstate, including information obtained from the device's various sensorsand input control devices 116; and location information concerning thedevice's location and/or attitude.

Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communication between varioushardware and software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with, the30-pin connector used on iPod® (trademark of Apple Inc.) devices.

Contact/motion module 130 optionally detects contact with touch screen112 (in conjunction with display controller 156) and othertouch-sensitive devices (e.g., a touchpad or physical click wheel).Contact/motion module 130 includes various software components forperforming various operations related to detection of contact, such asdetermining if contact has occurred (e.g., detecting a finger-downevent), determining an intensity of the contact (e.g., the force orpressure of the contact or a substitute for the force or pressure of thecontact), determining if there is movement of the contact and trackingthe movement across the touch-sensitive surface (e.g., detecting one ormore finger-dragging events), and determining if the contact has ceased(e.g., detecting a finger-up event or a break in contact).Contact/motion module 130 receives contact data from the touch-sensitivesurface. Determining movement of the point of contact, which isrepresented by a series of contact data, optionally includes determiningspeed (magnitude), velocity (magnitude and direction), and/or anacceleration (a change in magnitude and/or direction) of the point ofcontact. These operations are, optionally, applied to single contacts(e.g., one finger contacts) or to multiple simultaneous contacts (e.g.,“multitouch”/multiple finger contacts). In some embodiments,contact/motion module 130 and display controller 156 detect contact on atouchpad.

In some embodiments, contact/motion module 130 uses a set of one or moreintensity thresholds to determine whether an operation has beenperformed by a user (e.g., to determine whether a user has “clicked” onan icon). In some embodiments, at least a subset of the intensitythresholds are determined in accordance with software parameters (e.g.,the intensity thresholds are not determined by the activation thresholdsof particular physical actuators and can be adjusted without changingthe physical hardware of device 100). For example, a mouse “click”threshold of a trackpad or touch screen display can be set to any of alarge range of predefined threshold values without changing the trackpador touch screen display hardware. Additionally, in some implementations,a user of the device is provided with software settings for adjustingone or more of the set of intensity thresholds (e.g., by adjustingindividual intensity thresholds and/or by adjusting a plurality ofintensity thresholds at once with a system-level click “intensity”parameter).

Contact/motion module 130 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns (e.g., different motions, timings, and/or intensities ofdetected contacts). Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (liftoff) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (liftoff) event.

Graphics module 132 includes various known software components forrendering and displaying graphics on touch screen 112 or other display,including components for changing the visual impact (e.g., brightness,transparency, saturation, contrast, or other visual property) ofgraphics that are displayed. As used herein, the term “graphics”includes any object that can be displayed to a user, including, withoutlimitation, text, web pages, icons (such as user-interface objectsincluding soft keys), digital images, videos, animations, and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic is, optionally, assigned acorresponding code. Graphics module 132 receives, from applicationsetc., one or more codes specifying graphics to be displayed along with,if necessary, coordinate data and other graphic property data, and thengenerates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components forgenerating instructions used by tactile output generator(s) 167 toproduce tactile outputs at one or more locations on device 100 inresponse to user interactions with device 100.

-   -   Text input module 134, which is, optionally, a component of        graphics module 132, provides soft keyboards for entering text        in various applications (e.g., contacts 137, e-mail 140, IM 141,        browser 147, and any other application that needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing; to camera 143 as picture/video metadata;and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 136 optionally include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   Contacts module 137 (sometimes called an address book or contact        list);    -   Telephone module 138;    -   Video conference module 139;    -   E-mail client module 140;    -   Instant messaging (IM) module 141;    -   Workout support module 142;    -   Camera module 143 for still and/or video images;    -   Image management module 144;    -   Video player module;    -   Music player module;    -   Browser module 147;    -   Calendar module 148;    -   Widget modules 149, which optionally include one or more of:        weather widget 149-1, stocks widget 149-2, calculator widget        149-3, alarm clock widget 149-4, dictionary widget 149-5, and        other widgets obtained by the user, as well as user-created        widgets 149-6;    -   Widget creator module 150 for making user-created widgets 149-6;    -   Search module 151;    -   Video and music player module 152, which merges video player        module and music player module;    -   Notes module 153;    -   Map module 154; and/or    -   Online video module 155.

Examples of other applications 136 that are, optionally, stored inmemory 102 include other word processing applications, other imageediting applications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, contacts module 137 are, optionally, used to manage an address bookor contact list (e.g., stored in application internal state 192 ofcontacts module 137 in memory 102 or memory 370), including: addingname(s) to the address book; deleting name(s) from the address book;associating telephone number(s), e-mail address(es), physicaladdress(es) or other information with a name; associating an image witha name; categorizing and sorting names; providing telephone numbers ore-mail addresses to initiate and/or facilitate communications bytelephone 138, video conference module 139, e-mail 140, or IM 141; andso forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, contact/motionmodule 130, graphics module 132, and text input module 134, telephonemodule 138 are optionally, used to enter a sequence of characterscorresponding to a telephone number, access one or more telephonenumbers in contacts module 137, modify a telephone number that has beenentered, dial a respective telephone number, conduct a conversation, anddisconnect or hang up when the conversation is completed. As notedabove, the wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, optical sensor164, optical sensor controller 158, contact/motion module 130, graphicsmodule 132, text input module 134, contacts module 137, and telephonemodule 138, video conference module 139 includes executable instructionsto initiate, conduct, and terminate a video conference between a userand one or more other participants in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, e-mail client module 140 includes executableinstructions to create, send, receive, and manage e-mail in response touser instructions. In conjunction with image management module 144,e-mail client module 140 makes it very easy to create and send e-mailswith still or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, the instant messaging module 141 includes executableinstructions to enter a sequence of characters corresponding to aninstant message, to modify previously entered characters, to transmit arespective instant message (for example, using a Short Message Service(SMS) or Multimedia Message Service (MMS) protocol for telephony-basedinstant messages or using XMPP, SIMPLE, or IMPS for Internet-basedinstant messages), to receive instant messages, and to view receivedinstant messages. In some embodiments, transmitted and/or receivedinstant messages optionally include graphics, photos, audio files, videofiles and/or other attachments as are supported in an MMS and/or anEnhanced Messaging Service (EMS). As used herein, “instant messaging”refers to both telephony-based messages (e.g., messages sent using SMSor MMS) and Internet-based messages (e.g., messages sent using XMPP,SIMPLE, or IMPS).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, map module 154, and music playermodule, workout support module 142 includes executable instructions tocreate workouts (e.g., with time, distance, and/or calorie burninggoals); communicate with workout sensors (sports devices); receiveworkout sensor data; calibrate sensors used to monitor a workout; selectand play music for a workout; and display, store, and transmit workoutdata.

In conjunction with touch screen 112, display controller 156, opticalsensor(s) 164, optical sensor controller 158, contact/motion module 130,graphics module 132, and image management module 144, camera module 143includes executable instructions to capture still images or video(including a video stream) and store them into memory 102, modifycharacteristics of a still image or video, or delete a still image orvideo from memory 102.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, text input module 134,and camera module 143, image management module 144 includes executableinstructions to arrange, modify (e.g., edit), or otherwise manipulate,label, delete, present (e.g., in a digital slide show or album), andstore still and/or video images.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, browser module 147 includes executable instructions tobrowse the Internet in accordance with user instructions, includingsearching, linking to, receiving, and displaying web pages or portionsthereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, e-mail client module 140, and browser module 147,calendar module 148 includes executable instructions to create, display,modify, and store calendars and data associated with calendars (e.g.,calendar entries, to-do lists, etc.) in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, widget modules 149 aremini-applications that are, optionally, downloaded and used by a user(e.g., weather widget 149-1, stocks widget 149-2, calculator widget149-3, alarm clock widget 149-4, and dictionary widget 149-5) or createdby the user (e.g., user-created widget 149-6). In some embodiments, awidget includes an HTML (Hypertext Markup Language) file, a CSS(Cascading Style Sheets) file, and a JavaScript file. In someembodiments, a widget includes an XML (Extensible Markup Language) fileand a JavaScript file (e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, the widget creator module 150are, optionally, used by a user to create widgets (e.g., turning auser-specified portion of a web page into a widget).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, search module 151 includes executable instructions to search fortext, music, sound, image, video, and/or other files in memory 102 thatmatch one or more search criteria (e.g., one or more user-specifiedsearch terms) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, and browser module 147, video and musicplayer module 152 includes executable instructions that allow the userto download and play back recorded music and other sound files stored inone or more file formats, such as MP3 or AAC files, and executableinstructions to display, present, or otherwise play back videos (e.g.,on touch screen 112 or on an external, connected display via externalport 124). In some embodiments, device 100 optionally includes thefunctionality of an MP3 player, such as an iPod (trademark of AppleInc.).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, notes module 153 includes executable instructions to create andmanage notes, to-do lists, and the like in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, and browser module 147, map module 154are, optionally, used to receive, display, modify, and store maps anddata associated with maps (e.g., driving directions, data on stores andother points of interest at or near a particular location, and otherlocation-based data) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, text input module 134, e-mail clientmodule 140, and browser module 147, online video module 155 includesinstructions that allow the user to access, browse, receive (e.g., bystreaming and/or download), play back (e.g., on the touch screen or onan external, connected display via external port 124), send an e-mailwith a link to a particular online video, and otherwise manage onlinevideos in one or more file formats, such as H.264. In some embodiments,instant messaging module 141, rather than e-mail client module 140, isused to send a link to a particular online video. Additional descriptionof the online video application can be found in U.S. Provisional PatentApplication No. 60/936,562, “Portable Multifunction Device, Method, andGraphical User Interface for Playing Online Videos,” filed Jun. 20,2007, and U.S. patent application Ser. No. 11/968,067, “PortableMultifunction Device, Method, and Graphical User Interface for PlayingOnline Videos,” filed Dec. 31, 2007, the contents of which are herebyincorporated by reference in their entirety.

Each of the above-identified modules and applications corresponds to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (e.g., sets of instructions) need notbe implemented as separate software programs, procedures, or modules,and thus various subsets of these modules are, optionally, combined orotherwise rearranged in various embodiments. For example, video playermodule is, optionally, combined with music player module into a singlemodule (e.g., video and music player module 152, FIG. 1A). In someembodiments, memory 102 optionally stores a subset of the modules anddata structures identified above. Furthermore, memory 102 optionallystores additional modules and data structures not described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 is, optionally, reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some embodiments, the touchpad, when touched by theuser, navigates device 100 to a main, home, or root menu from any userinterface that is displayed on device 100. In such embodiments, a “menubutton” is implemented using a touchpad. In some other embodiments, themenu button is a physical push button or other physical input controldevice instead of a touchpad.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (FIG. 1A) or 370 (FIG. 3 ) includes event sorter 170 (e.g.,in operating system 126) and a respective application 136-1 (e.g., anyof the aforementioned applications 137-151, 155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch-sensitivedisplay 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display 112, as part of a multi-touchgesture). Peripherals interface 118 transmits information it receivesfrom I/O subsystem 106 or a sensor, such as proximity sensor 166,accelerometer(s) 168, and/or microphone 113 (through audio circuitry110). Information that peripherals interface 118 receives from I/Osubsystem 106 includes information from touch-sensitive display 112 or atouch-sensitive surface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripherals interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more viewswhen touch-sensitive display 112 displays more than one view. Views aremade up of controls and other elements that a user can see on thedisplay.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected optionally correspond to programmatic levelswithin a programmatic or view hierarchy of the application. For example,the lowest level view in which a touch is detected is, optionally,called the hit view, and the set of events that are recognized as properinputs are, optionally, determined based, at least in part, on the hitview of the initial touch that begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (e.g., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule 172, the hit view typically receives all sub-events related tothe same touch or input source for which it was identified as the hitview.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver 182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180. Typically, a respective application view 191 includes a pluralityof event recognizers 180. In other embodiments, one or more of eventrecognizers 180 are part of a separate module, such as a user interfacekit (not shown) or a higher level object from which application 136-1inherits methods and other properties. In some embodiments, a respectiveevent handler 190 includes one or more of: data updater 176, objectupdater 177, GUI updater 178, and/or event data 179 received from eventsorter 170. Event handler 190 optionally utilizes or calls data updater176, object updater 177, or GUI updater 178 to update the applicationinternal state 192. Alternatively, one or more of the application views191 include one or more respective event handlers 190. Also, in someembodiments, one or more of data updater 176, object updater 177, andGUI updater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170 and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which optionally include sub-event deliveryinstructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch, the eventinformation optionally also includes speed and direction of thesub-event. In some embodiments, events include rotation of the devicefrom one orientation to another (e.g., from a portrait orientation to alandscape orientation, or vice versa), and the event informationincludes corresponding information about the current orientation (alsocalled device attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events inan event (187) include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (187-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first liftoff (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second liftoff (touchend) for a predetermined phase. In another example, the definition forevent 2 (187-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay 112, and liftoff of the touch (touch end). In some embodiments,the event also includes information for one or more associated eventhandlers 190.

In some embodiments, event definition 187 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display 112, when a touch is detected on touch-sensitivedisplay 112, event comparator 184 performs a hit test to determine whichof the three user-interface objects is associated with the touch(sub-event). If each displayed object is associated with a respectiveevent handler 190, the event comparator uses the result of the hit testto determine which event handler 190 should be activated. For example,event comparator 184 selects an event handler associated with thesub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event (187) alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers interact, or are enabled to interact, with one another. Insome embodiments, metadata 183 includes configurable properties, flags,and/or lists that indicate whether sub-events are delivered to varyinglevels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module. In some embodiments, object updater 177 creates andupdates objects used in application 136-1. For example, object updater177 creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc. on touchpads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen 112 in accordance with some embodiments. The touch screenoptionally displays one or more graphics within user interface (UI) 200.In this embodiment, as well as others described below, a user is enabledto select one or more of the graphics by making a gesture on thegraphics, for example, with one or more fingers 202 (not drawn to scalein the figure) or one or more styluses 203 (not drawn to scale in thefigure). In some embodiments, selection of one or more graphics occurswhen the user breaks contact with the one or more graphics. In someembodiments, the gesture optionally includes one or more taps, one ormore swipes (from left to right, right to left, upward and/or downward),and/or a rolling of a finger (from right to left, left to right, upwardand/or downward) that has made contact with device 100. In someimplementations or circumstances, inadvertent contact with a graphicdoes not select the graphic. For example, a swipe gesture that sweepsover an application icon optionally does not select the correspondingapplication when the gesture corresponding to selection is a tap.

Device 100 optionally also include one or more physical buttons, such as“home” or menu button 204. As described previously, menu button 204 is,optionally, used to navigate to any application 136 in a set ofapplications that are, optionally, executed on device 100.Alternatively, in some embodiments, the menu button is implemented as asoft key in a GUI displayed on touch screen 112.

In some embodiments, device 100 includes touch screen 112, menu button204, push button 206 for powering the device on/off and locking thedevice, volume adjustment button(s) 208, subscriber identity module(SIM) card slot 210, headset jack 212, and docking/charging externalport 124. Push button 206 is, optionally, used to turn the power on/offon the device by depressing the button and holding the button in thedepressed state for a predefined time interval; to lock the device bydepressing the button and releasing the button before the predefinedtime interval has elapsed; and/or to unlock the device or initiate anunlock process. In an alternative embodiment, device 100 also acceptsverbal input for activation or deactivation of some functions throughmicrophone 113. Device 100 also, optionally, includes one or morecontact intensity sensors 165 for detecting intensity of contacts ontouch screen 112 and/or one or more tactile output generators 167 forgenerating tactile outputs for a user of device 100.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 300 need not be portable. In some embodiments,device 300 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 300 typically includesone or more processing units (CPUs) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. Communication buses 320optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 300 includes input/output (I/O) interface 330 comprising display340, which is typically a touch screen display. I/O interface 330 alsooptionally includes a keyboard and/or mouse (or other pointing device)350 and touchpad 355, tactile output generator 357 for generatingtactile outputs on device 300 (e.g., similar to tactile outputgenerator(s) 167 described above with reference to FIG. 1A), sensors 359(e.g., optical, acceleration, proximity, touch-sensitive, and/or contactintensity sensors similar to contact intensity sensor(s) 165 describedabove with reference to FIG. 1A). Memory 370 includes high-speed randomaccess memory, such as DRAM, SRAM, DDR RAM, or other random access solidstate memory devices; and optionally includes non-volatile memory, suchas one or more magnetic disk storage devices, optical disk storagedevices, flash memory devices, or other non-volatile solid state storagedevices. Memory 370 optionally includes one or more storage devicesremotely located from CPU(s) 310. In some embodiments, memory 370 storesprograms, modules, and data structures analogous to the programs,modules, and data structures stored in memory 102 of portablemultifunction device 100 (FIG. 1A), or a subset thereof. Furthermore,memory 370 optionally stores additional programs, modules, and datastructures not present in memory 102 of portable multifunction device100. For example, memory 370 of device 300 optionally stores drawingmodule 380, presentation module 382, word processing module 384, websitecreation module 386, disk authoring module 388, and/or spreadsheetmodule 390, while memory 102 of portable multifunction device 100 (FIG.1A) optionally does not store these modules.

Each of the above-identified elements in FIG. 3 is, optionally, storedin one or more of the previously mentioned memory devices. Each of theabove-identified modules corresponds to a set of instructions forperforming a function described above. The above-identified modules orprograms (e.g., sets of instructions) need not be implemented asseparate software programs, procedures, or modules, and thus varioussubsets of these modules are, optionally, combined or otherwiserearranged in various embodiments. In some embodiments, memory 370optionally stores a subset of the modules and data structures identifiedabove. Furthermore, memory 370 optionally stores additional modules anddata structures not described above.

Attention is now directed towards embodiments of user interfaces thatare, optionally, implemented on, for example, portable multifunctiondevice 100.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on portable multifunction device 100 in accordance withsome embodiments. Similar user interfaces are, optionally, implementedon device 300. In some embodiments, user interface 400 includes thefollowing elements, or a subset or superset thereof:

-   -   Signal strength indicator(s) 402 for wireless communication(s),        such as cellular and Wi-Fi signals;    -   Time 404;    -   Bluetooth indicator 405;    -   Battery status indicator 406;    -   Tray 408 with icons for frequently used applications, such as:        -   Icon 416 for telephone module 138, labeled “Phone,” which            optionally includes an indicator 414 of the number of missed            calls or voicemail messages;        -   Icon 418 for e-mail client module 140, labeled “Mail,” which            optionally includes an indicator 410 of the number of unread            e-mails;        -   Icon 420 for browser module 147, labeled “Browser;” and        -   Icon 422 for video and music player module 152, also            referred to as iPod (trademark of Apple Inc.) module 152,            labeled “iPod;” and    -   Icons for other applications, such as:        -   Icon 424 for IM module 141, labeled “Messages;”        -   Icon 426 for calendar module 148, labeled “Calendar;”        -   Icon 428 for image management module 144, labeled “Photos;”        -   Icon 430 for camera module 143, labeled “Camera;”        -   Icon 432 for online video module 155, labeled “Online            Video;”        -   Icon 434 for stocks widget 149-2, labeled “Stocks;”        -   Icon 436 for map module 154, labeled “Maps;”        -   Icon 438 for weather widget 149-1, labeled “Weather;”        -   Icon 440 for alarm clock widget 149-4, labeled “Clock;”        -   Icon 442 for workout support module 142, labeled “Workout            Support;”        -   Icon 444 for notes module 153, labeled “Notes;” and        -   Icon 446 for a settings application or module, labeled            “Settings,” which provides access to settings for device 100            and its various applications 136.

It should be noted that the icon labels illustrated in FIG. 4A aremerely exemplary. For example, icon 422 for video and music playermodule 152 is labeled “Music” or “Music Player.” Other labels are,optionally, used for various application icons. In some embodiments, alabel for a respective application icon includes a name of anapplication corresponding to the respective application icon. In someembodiments, a label for a particular application icon is distinct froma name of an application corresponding to the particular applicationicon.

FIG. 4B illustrates an exemplary user interface on a device (e.g.,device 300, FIG. 3 ) with a touch-sensitive surface 451 (e.g., a tabletor touchpad 355, FIG. 3 ) that is separate from the display 450 (e.g.,touch screen display 112). Device 300 also, optionally, includes one ormore contact intensity sensors (e.g., one or more of sensors 359) fordetecting intensity of contacts on touch-sensitive surface 451 and/orone or more tactile output generators 357 for generating tactile outputsfor a user of device 300.

Although some of the examples that follow will be given with referenceto inputs on touch screen display 112 (where the touch-sensitive surfaceand the display are combined), in some embodiments, the device detectsinputs on a touch-sensitive surface that is separate from the display,as shown in FIG. 4B. In some embodiments, the touch-sensitive surface(e.g., 451 in FIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) thatcorresponds to a primary axis (e.g., 453 in FIG. 4B) on the display(e.g., 450). In accordance with these embodiments, the device detectscontacts (e.g., 460 and 462 in FIG. 4B) with the touch-sensitive surface451 at locations that correspond to respective locations on the display(e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470).In this way, user inputs (e.g., contacts 460 and 462, and movementsthereof) detected by the device on the touch-sensitive surface (e.g.,451 in FIG. 4B) are used by the device to manipulate the user interfaceon the display (e.g., 450 in FIG. 4B) of the multifunction device whenthe touch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures), it should be understood that, in someembodiments, one or more of the finger inputs are replaced with inputfrom another input device (e.g., a mouse-based input or stylus input).For example, a swipe gesture is, optionally, replaced with a mouse click(e.g., instead of a contact) followed by movement of the cursor alongthe path of the swipe (e.g., instead of movement of the contact). Asanother example, a tap gesture is, optionally, replaced with a mouseclick while the cursor is located over the location of the tap gesture(e.g., instead of detection of the contact followed by ceasing to detectthe contact). Similarly, when multiple user inputs are simultaneouslydetected, it should be understood that multiple computer mice are,optionally, used simultaneously, or a mouse and finger contacts are,optionally, used simultaneously.

FIG. 5A illustrates exemplary personal electronic device 500. Device 500includes body 502. In some embodiments, device 500 can include some orall of the features described with respect to devices 100 and 300 (e.g.,FIGS. 1A-4B). In some embodiments, device 500 has touch-sensitivedisplay screen 504, hereafter touch screen 504. Alternatively, or inaddition to touch screen 504, device 500 has a display and atouch-sensitive surface. As with devices 100 and 300, in someembodiments, touch screen 504 (or the touch-sensitive surface)optionally includes one or more intensity sensors for detectingintensity of contacts (e.g., touches) being applied. The one or moreintensity sensors of touch screen 504 (or the touch-sensitive surface)can provide output data that represents the intensity of touches. Theuser interface of device 500 can respond to touches based on theirintensity, meaning that touches of different intensities can invokedifferent user interface operations on device 500.

Exemplary techniques for detecting and processing touch intensity arefound, for example, in related applications: International PatentApplication Serial No. PCT/US2013/040061, titled “Device, Method, andGraphical User Interface for Displaying User Interface ObjectsCorresponding to an Application,” filed May 8, 2013, published as WIPOPublication No. WO/2013/169849, and International Patent ApplicationSerial No. PCT/US2013/069483, titled “Device, Method, and Graphical UserInterface for Transitioning Between Touch Input to Display OutputRelationships,” filed Nov. 11, 2013, published as WIPO Publication No.WO/2014/105276, each of which is hereby incorporated by reference intheir entirety.

In some embodiments, device 500 has one or more input mechanisms 506 and508. Input mechanisms 506 and 508, if included, can be physical.Examples of physical input mechanisms include push buttons and rotatablemechanisms. In some embodiments, device 500 has one or more attachmentmechanisms. Such attachment mechanisms, if included, can permitattachment of device 500 with, for example, hats, eyewear, earrings,necklaces, shirts, jackets, bracelets, watch straps, chains, trousers,belts, shoes, purses, backpacks, and so forth. These attachmentmechanisms permit device 500 to be worn by a user.

FIG. 5B depicts exemplary personal electronic device 500. In someembodiments, device 500 can include some or all of the componentsdescribed with respect to FIGS. 1A, 1B, and 3 . Device 500 has bus 512that operatively couples I/O section 514 with one or more computerprocessors 516 and memory 518. I/O section 514 can be connected todisplay 504, which can have touch-sensitive component 522 and,optionally, intensity sensor 524 (e.g., contact intensity sensor). Inaddition, I/O section 514 can be connected with communication unit 530for receiving application and operating system data, using Wi-Fi,Bluetooth, near field communication (NFC), cellular, and/or otherwireless communication techniques. Device 500 can include inputmechanisms 506 and/or 508. Input mechanism 506 is, optionally, arotatable input device or a depressible and rotatable input device, forexample. Input mechanism 508 is, optionally, a button, in some examples.

Input mechanism 508 is, optionally, a microphone, in some examples.Personal electronic device 500 optionally includes various sensors, suchas GPS sensor 532, accelerometer 534, directional sensor 540 (e.g.,compass), gyroscope 536, motion sensor 538, and/or a combinationthereof, all of which can be operatively connected to I/O section 514.

Memory 518 of personal electronic device 500 can include one or morenon-transitory computer-readable storage mediums, for storingcomputer-executable instructions, which, when executed by one or morecomputer processors 516, for example, can cause the computer processorsto perform the techniques described below, including processes 700, 800,1000, 1500, 1600, and 1800 (FIGS. 7A-8G, 10A-10C, 15A-16D, and 18 ). Acomputer-readable storage medium can be any medium that can tangiblycontain or store computer-executable instructions for use by or inconnection with the instruction execution system, apparatus, or device.In some examples, the storage medium is a transitory computer-readablestorage medium. In some examples, the storage medium is a non-transitorycomputer-readable storage medium. The non-transitory computer-readablestorage medium can include, but is not limited to, magnetic, optical,and/or semiconductor storages. Examples of such storage include magneticdisks, optical discs based on CD, DVD, or Blu-ray technologies, as wellas persistent solid-state memory such as flash, solid-state drives, andthe like. Personal electronic device 500 is not limited to thecomponents and configuration of FIG. 5B, but can include other oradditional components in multiple configurations.

As used here, the term “affordance” refers to a user-interactivegraphical user interface object that is, optionally, displayed on thedisplay screen of devices 100, 300, and/or 500 (FIGS. 1A, 3, and 5A-5B).For example, an image (e.g., icon), a button, and text (e.g., hyperlink)each optionally constitute an affordance.

As used herein, the term “focus selector” refers to an input elementthat indicates a current part of a user interface with which a user isinteracting. In some implementations that include a cursor or otherlocation marker, the cursor acts as a “focus selector” so that when aninput (e.g., a press input) is detected on a touch-sensitive surface(e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B)while the cursor is over a particular user interface element (e.g., abutton, window, slider, or other user interface element), the particularuser interface element is adjusted in accordance with the detectedinput. In some implementations that include a touch screen display(e.g., touch-sensitive display system 112 in FIG. 1A or touch screen 112in FIG. 4A) that enables direct interaction with user interface elementson the touch screen display, a detected contact on the touch screen actsas a “focus selector” so that when an input (e.g., a press input by thecontact) is detected on the touch screen display at a location of aparticular user interface element (e.g., a button, window, slider, orother user interface element), the particular user interface element isadjusted in accordance with the detected input. In some implementations,focus is moved from one region of a user interface to another region ofthe user interface without corresponding movement of a cursor ormovement of a contact on a touch screen display (e.g., by using a tabkey or arrow keys to move focus from one button to another button); inthese implementations, the focus selector moves in accordance withmovement of focus between different regions of the user interface.Without regard to the specific form taken by the focus selector, thefocus selector is generally the user interface element (or contact on atouch screen display) that is controlled by the user so as tocommunicate the user's intended interaction with the user interface(e.g., by indicating, to the device, the element of the user interfacewith which the user is intending to interact). For example, the locationof a focus selector (e.g., a cursor, a contact, or a selection box) overa respective button while a press input is detected on thetouch-sensitive surface (e.g., a touchpad or touch screen) will indicatethat the user is intending to activate the respective button (as opposedto other user interface elements shown on a display of the device).

As used in the specification and claims, the term “characteristicintensity” of a contact refers to a characteristic of the contact basedon one or more intensities of the contact. In some embodiments, thecharacteristic intensity is based on multiple intensity samples. Thecharacteristic intensity is, optionally, based on a predefined number ofintensity samples, or a set of intensity samples collected during apredetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10seconds) relative to a predefined event (e.g., after detecting thecontact, prior to detecting liftoff of the contact, before or afterdetecting a start of movement of the contact, prior to detecting an endof the contact, before or after detecting an increase in intensity ofthe contact, and/or before or after detecting a decrease in intensity ofthe contact). A characteristic intensity of a contact is, optionally,based on one or more of: a maximum value of the intensities of thecontact, a mean value of the intensities of the contact, an averagevalue of the intensities of the contact, a top 10 percentile value ofthe intensities of the contact, a value at the half maximum of theintensities of the contact, a value at the 90 percent maximum of theintensities of the contact, or the like. In some embodiments, theduration of the contact is used in determining the characteristicintensity (e.g., when the characteristic intensity is an average of theintensity of the contact over time). In some embodiments, thecharacteristic intensity is compared to a set of one or more intensitythresholds to determine whether an operation has been performed by auser. For example, the set of one or more intensity thresholdsoptionally includes a first intensity threshold and a second intensitythreshold. In this example, a contact with a characteristic intensitythat does not exceed the first threshold results in a first operation, acontact with a characteristic intensity that exceeds the first intensitythreshold and does not exceed the second intensity threshold results ina second operation, and a contact with a characteristic intensity thatexceeds the second threshold results in a third operation. In someembodiments, a comparison between the characteristic intensity and oneor more thresholds is used to determine whether or not to perform one ormore operations (e.g., whether to perform a respective operation orforgo performing the respective operation), rather than being used todetermine whether to perform a first operation or a second operation.

FIG. 5C illustrates detecting a plurality of contacts 552A-552E ontouch-sensitive display screen 504 with a plurality of intensity sensors524A-524D. FIG. 5C additionally includes intensity diagrams that showthe current intensity measurements of the intensity sensors 524A-524Drelative to units of intensity. In this example, the intensitymeasurements of intensity sensors 524A and 524D are each 9 units ofintensity, and the intensity measurements of intensity sensors 524B and524C are each 7 units of intensity. In some implementations, anaggregate intensity is the sum of the intensity measurements of theplurality of intensity sensors 524A-524D, which in this example is 32intensity units. In some embodiments, each contact is assigned arespective intensity that is a portion of the aggregate intensity. FIG.5D illustrates assigning the aggregate intensity to contacts 552A-552Ebased on their distance from the center of force 554. In this example,each of contacts 552A, 552B, and 552E are assigned an intensity ofcontact of 8 intensity units of the aggregate intensity, and each ofcontacts 552C and 552D are assigned an intensity of contact of 4intensity units of the aggregate intensity. More generally, in someimplementations, each contact j is assigned a respective intensity Ijthat is a portion of the aggregate intensity, A, in accordance with apredefined mathematical function, Ij=A·(Dj/ΣDi), where Dj is thedistance of the respective contact j to the center of force, and ΣDi isthe sum of the distances of all the respective contacts (e.g., i=1 tolast) to the center of force. The operations described with reference toFIGS. 5C-5D can be performed using an electronic device similar oridentical to device 100, 300, or 500. In some embodiments, acharacteristic intensity of a contact is based on one or moreintensities of the contact. In some embodiments, the intensity sensorsare used to determine a single characteristic intensity (e.g., a singlecharacteristic intensity of a single contact). It should be noted thatthe intensity diagrams are not part of a displayed user interface, butare included in FIGS. 5C-5D to aid the reader.

In some embodiments, a portion of a gesture is identified for purposesof determining a characteristic intensity. For example, atouch-sensitive surface optionally receives a continuous swipe contacttransitioning from a start location and reaching an end location, atwhich point the intensity of the contact increases. In this example, thecharacteristic intensity of the contact at the end location is,optionally, based on only a portion of the continuous swipe contact, andnot the entire swipe contact (e.g., only the portion of the swipecontact at the end location). In some embodiments, a smoothing algorithmis, optionally, applied to the intensities of the swipe contact prior todetermining the characteristic intensity of the contact. For example,the smoothing algorithm optionally includes one or more of: anunweighted sliding-average smoothing algorithm, a triangular smoothingalgorithm, a median filter smoothing algorithm, and/or an exponentialsmoothing algorithm. In some circumstances, these smoothing algorithmseliminate narrow spikes or dips in the intensities of the swipe contactfor purposes of determining a characteristic intensity.

The intensity of a contact on the touch-sensitive surface is,optionally, characterized relative to one or more intensity thresholds,such as a contact-detection intensity threshold, a light press intensitythreshold, a deep press intensity threshold, and/or one or more otherintensity thresholds. In some embodiments, the light press intensitythreshold corresponds to an intensity at which the device will performoperations typically associated with clicking a button of a physicalmouse or a trackpad. In some embodiments, the deep press intensitythreshold corresponds to an intensity at which the device will performoperations that are different from operations typically associated withclicking a button of a physical mouse or a trackpad. In someembodiments, when a contact is detected with a characteristic intensitybelow the light press intensity threshold (e.g., and above a nominalcontact-detection intensity threshold below which the contact is nolonger detected), the device will move a focus selector in accordancewith movement of the contact on the touch-sensitive surface withoutperforming an operation associated with the light press intensitythreshold or the deep press intensity threshold. Generally, unlessotherwise stated, these intensity thresholds are consistent betweendifferent sets of user interface figures.

An increase of characteristic intensity of the contact from an intensitybelow the light press intensity threshold to an intensity between thelight press intensity threshold and the deep press intensity thresholdis sometimes referred to as a “light press” input. An increase ofcharacteristic intensity of the contact from an intensity below the deeppress intensity threshold to an intensity above the deep press intensitythreshold is sometimes referred to as a “deep press” input. An increaseof characteristic intensity of the contact from an intensity below thecontact-detection intensity threshold to an intensity between thecontact-detection intensity threshold and the light press intensitythreshold is sometimes referred to as detecting the contact on thetouch-surface. A decrease of characteristic intensity of the contactfrom an intensity above the contact-detection intensity threshold to anintensity below the contact-detection intensity threshold is sometimesreferred to as detecting liftoff of the contact from the touch-surface.In some embodiments, the contact-detection intensity threshold is zero.In some embodiments, the contact-detection intensity threshold isgreater than zero.

In some embodiments described herein, one or more operations areperformed in response to detecting a gesture that includes a respectivepress input or in response to detecting the respective press inputperformed with a respective contact (or a plurality of contacts), wherethe respective press input is detected based at least in part ondetecting an increase in intensity of the contact (or plurality ofcontacts) above a press-input intensity threshold. In some embodiments,the respective operation is performed in response to detecting theincrease in intensity of the respective contact above the press-inputintensity threshold (e.g., a “down stroke” of the respective pressinput). In some embodiments, the press input includes an increase inintensity of the respective contact above the press-input intensitythreshold and a subsequent decrease in intensity of the contact belowthe press-input intensity threshold, and the respective operation isperformed in response to detecting the subsequent decrease in intensityof the respective contact below the press-input threshold (e.g., an “upstroke” of the respective press input).

FIGS. 5E-5H illustrate detection of a gesture that includes a pressinput that corresponds to an increase in intensity of a contact 562 froman intensity below a light press intensity threshold (e.g., “IT_(L)”) inFIG. 5E, to an intensity above a deep press intensity threshold (e.g.,“IT_(D)”) in FIG. 5H. The gesture performed with contact 562 is detectedon touch-sensitive surface 560 while cursor 576 is displayed overapplication icon 572B corresponding to App 2, on a displayed userinterface 570 that includes application icons 572A-572D displayed inpredefined region 574. In some embodiments, the gesture is detected ontouch-sensitive display 504. The intensity sensors detect the intensityof contacts on touch-sensitive surface 560. The device determines thatthe intensity of contact 562 peaked above the deep press intensitythreshold (e.g., “IT_(D)”). Contact 562 is maintained on touch-sensitivesurface 560. In response to the detection of the gesture, and inaccordance with contact 562 having an intensity that goes above the deeppress intensity threshold (e.g., “IT_(D)”) during the gesture,reduced-scale representations 578A-578C (e.g., thumbnails) of recentlyopened documents for App 2 are displayed, as shown in FIGS. 5F-5H. Insome embodiments, the intensity, which is compared to the one or moreintensity thresholds, is the characteristic intensity of a contact. Itshould be noted that the intensity diagram for contact 562 is not partof a displayed user interface, but is included in FIGS. 5E-5H to aid thereader.

In some embodiments, the display of representations 578A-578C includesan animation. For example, representation 578A is initially displayed inproximity of application icon 572B, as shown in FIG. 5F. As theanimation proceeds, representation 578A moves upward and representation578B is displayed in proximity of application icon 572B, as shown inFIG. 5G. Then, representations 578A moves upward, 578B moves upwardtoward representation 578A, and representation 578C is displayed inproximity of application icon 572B, as shown in FIG. 5H. Representations578A-578C form an array above icon 572B. In some embodiments, theanimation progresses in accordance with an intensity of contact 562, asshown in FIGS. 5F-5G, where the representations 578A-578C appear andmove upwards as the intensity of contact 562 increases toward the deeppress intensity threshold (e.g., “IT_(D)”). In some embodiments, theintensity, on which the progress of the animation is based, is thecharacteristic intensity of the contact. The operations described withreference to FIGS. 5E-5H can be performed using an electronic devicesimilar or identical to device 100, 300, or 500.

In some embodiments, the device employs intensity hysteresis to avoidaccidental inputs sometimes termed “jitter,” where the device defines orselects a hysteresis intensity threshold with a predefined relationshipto the press-input intensity threshold (e.g., the hysteresis intensitythreshold is X intensity units lower than the press-input intensitythreshold or the hysteresis intensity threshold is 75%, 90%, or somereasonable proportion of the press-input intensity threshold). Thus, insome embodiments, the press input includes an increase in intensity ofthe respective contact above the press-input intensity threshold and asubsequent decrease in intensity of the contact below the hysteresisintensity threshold that corresponds to the press-input intensitythreshold, and the respective operation is performed in response todetecting the subsequent decrease in intensity of the respective contactbelow the hysteresis intensity threshold (e.g., an “up stroke” of therespective press input). Similarly, in some embodiments, the press inputis detected only when the device detects an increase in intensity of thecontact from an intensity at or below the hysteresis intensity thresholdto an intensity at or above the press-input intensity threshold and,optionally, a subsequent decrease in intensity of the contact to anintensity at or below the hysteresis intensity, and the respectiveoperation is performed in response to detecting the press input (e.g.,the increase in intensity of the contact or the decrease in intensity ofthe contact, depending on the circumstances).

For ease of explanation, the descriptions of operations performed inresponse to a press input associated with a press-input intensitythreshold or in response to a gesture including the press input are,optionally, triggered in response to detecting either: an increase inintensity of a contact above the press-input intensity threshold, anincrease in intensity of a contact from an intensity below thehysteresis intensity threshold to an intensity above the press-inputintensity threshold, a decrease in intensity of the contact below thepress-input intensity threshold, and/or a decrease in intensity of thecontact below the hysteresis intensity threshold corresponding to thepress-input intensity threshold. Additionally, in examples where anoperation is described as being performed in response to detecting adecrease in intensity of a contact below the press-input intensitythreshold, the operation is, optionally, performed in response todetecting a decrease in intensity of the contact below a hysteresisintensity threshold corresponding to, and lower than, the press-inputintensity threshold.

As used herein, an “installed application” refers to a softwareapplication that has been downloaded onto an electronic device (e.g.,devices 100, 300, and/or 500) and is ready to be launched (e.g., becomeopened) on the device. In some embodiments, a downloaded applicationbecomes an installed application by way of an installation program thatextracts program portions from a downloaded package and integrates theextracted portions with the operating system of the computer system.

As used herein, the terms “open application” or “executing application”refer to a software application with retained state information (e.g.,as part of device/global internal state 157 and/or application internalstate 192). An open or executing application is, optionally, any one ofthe following types of applications:

-   -   an active application, which is currently displayed on a display        screen of the device that the application is being used on;    -   a background application (or background processes), which is not        currently displayed, but one or more processes for the        application are being processed by one or more processors; and    -   a suspended or hibernated application, which is not running, but        has state information that is stored in memory (volatile and        non-volatile, respectively) and that can be used to resume        execution of the application.

As used herein, the term “closed application” refers to softwareapplications without retained state information (e.g., state informationfor closed applications is not stored in a memory of the device).Accordingly, closing an application includes stopping and/or removingapplication processes for the application and removing state informationfor the application from the memory of the device. Generally, opening asecond application while in a first application does not close the firstapplication. When the second application is displayed and the firstapplication ceases to be displayed, the first application becomes abackground application.

Attention is now directed towards embodiments of providingcontext-specific user interfaces and associated processes that may beimplemented on a portable multifunction device with a display and atouch-sensitive surface, such as devices 100, 300, and/or 500 (FIGS. 1A,3 , and/or 5A).

The following examples illustrate exemplary embodiments ofcontext-specific user interfaces. Described herein are overall conceptsrelated to interactive and/or customizable context-specific userinterfaces. It is noted that the context-specific user interfacesdescribed herein are editable in a number of ways. A user interface maydisplay or otherwise indicate various types of information related totime, and the type(s) of information may be customizable by the user. Auser interface may include aspects such as colors, density of display,and complications (or lack of complications) that are also customizable.As used here, consistent with its accepted meaning in art, acomplication refers to any clock face feature other than those used toindicate the hours and minutes of a time (e.g., clock hands orhour/minute indications). Complications may provide different types ofinformation to a user, such as data obtained from an application, andthe information conveyed to a user by a complication is alsocustomizable, as described below. In some embodiments, a complicationmay also serve as an affordance for launching an application. Additionaldescriptions of context-specific user interfaces, as well as featuresthereof and techniques related thereto (e.g., editing and/or selectingcontext-specific user interfaces), are found in International PatentApplication Serial No. PCT/US2015/034604, titled “Context-Specific UserInterfaces,” filed Jun. 7, 2015, published as WIPO Publication No.WO/2016/022203; International Patent Application Serial No.PCT/US2015/034606, titled “Context-Specific User Interfaces,” filed Jun.7, 2015, published as WIPO Publication No. WO/2016/022204; andInternational Patent Application Serial No. PCT/US2015/034607, titled“Context-Specific User Interfaces,” filed Jun. 7, 2015, published asWIPO Publication No. WO/2016/022205; each of which is incorporated byreference herein in its entirety.

As described supra, users may wish to view different types ofinformation in different contexts (e.g., throughout the day) using aportable multifunction device. Widgets dedicated to a particularapplication can display specific sets of information from theapplication, but if the user is not interested in that information orapplication at a particular time, the information is taking up screen“real estate” that could be used to provide more immediately relevantinformation. Therefore, providing application information based ontemporal context, and/or not limited by the particular application fromwhich the information is obtained, provides a more efficient interfacethat allows the user to view the right information at the right time,thereby reducing the number of inputs required to access theinformation, decreasing demands on battery life (e.g., to power thedisplay), and making more efficient use of screen “real estate.”

FIGS. 6A-6V show exemplary context-specific user interfaces that may beoperated on device 600. Device 600 may be device 100, 300, or 500 insome embodiments. The electronic device has a display 602 (e.g., 504).In some embodiments, display 602 is a touch-sensitive display. In someembodiments, device 600 includes rotatable input mechanism 610 a (e.g.,506) and/or input mechanism or button 610 b (e.g., 508).

In FIG. 6A, device 600 displays a context-specific user interface ondisplay 602. This exemplary context-specific user interface includescurrent time indicator 604 (e.g., a digital clock). Indicator 604 canoptionally include a variety of features or aspects that areindependently editable or configurable by the user.

In addition, the context-specific user interface also includescomplications 612 614. In some embodiments, complications 612 and/or 614obtain data and display information from one or more applications. Insome embodiments, the displayed information can be updated, e.g., inaccordance with updates to data obtained from the application. Forexample, as shown in FIG. 6A, complication 612 can display informationfrom a calendar application (e.g., date and/or day of the week). In someembodiments, complication 614 does not display information updated inaccordance with updates to data obtained from the application, butrather displays a static representation of the application.

The user interface screen displayed in FIG. 6A also includes platters606 and 608. Platters 606 and 608 are each associated with anapplication. In this example, platter 606 is associated with a weatherapplication, and platter 608 is associated with a calendar application.Platter 606 displays a set of information obtained from the weatherapplication: the time of a predicted change in weather conditions ortime of predicted inclement weather conditions, as well as textual andgraphical indications of the weather conditions. Platter 608 displays aset of information obtained from the calendar application: the time ofan upcoming calendar event, and indications of the event name andlocation. Platter 606 is displayed as larger and/or appearing closer tothe user to emphasize its information (e.g., its temporal context(1:00-2:00 PM) is closer to the current time (10:09) than the temporalcontext of platter 608 (4:30-5:30 PM)).

Both platters 606 and 608 display information related to a temporalcontext of the current day. As used herein, a “temporal context” canrelate to a time attached to a set of information by the user (e.g., thetime of a calendar event), a time attached to a set of information by anexternal data source (e.g., the time of a predicted change in weather,based on data obtained from an external server), or a time attached to aset of information by an electronic device of the present disclosure(e.g., device 600). For example, as described in greater detail infra,device 600 can designate a time of day to surface a set of informationto the user, such as a reminder to breathe or engage in exercise.

Platters 606 and 608 are selected by device 600 for display based, atleast in part, on temporal context of the current day. Each represents adifferent application. Thus, information obtained from variousapplications can be presented to the user and optionally ordered bytemporal context. This allows the user to view information obtained fromone or more applications at a glance when it is relevant, rather thanallocating screen “real estate” to dedicated information and/orapplications that are not equally relevant throughout the day. In someembodiments, concurrently displayed platters can represent the sameapplication (e.g., two platters representing sets of calendarapplication-related information related to different temporal contexts).

To view information related to later temporal contexts, the user rotatesthe rotatable input mechanism 610 a (e.g., scroll 616 a; FIG. 6B).Scroll indicator 618 a is also displayed adjacent to 610 a on display602 to indicate to the user how many platters are displayable, and theposition of the currently displayed platter(s) in a series ofdisplayable platters. In some embodiments, scroll indicator 618 a isdisplayed in response to detecting scroll 616 a, thereby indicating tothe user that additional information can be viewed using rotationalinputs through rotatable input mechanism 610 a.

In response to detecting scroll 616 a, as shown in FIG. 6C, platters 606and 608 are translated on-screen, and platter 608 now appears largerand/or closer to the user. In addition, platter 620 is displayed at thebottom of display 602. Platter 620 is associated with a navigationapplication and displays a set of information obtained from thenavigation application (e.g., the time of a predicted change in trafficconditions, such as a time of worsening predicted traffic or a typicaltime of day when the user is driving or taking public transportation).Platter 620 displays information related to a temporal context of thecurrent day at the same time or later than the set of information shownin platter 608. The scroll indicator (e.g., 618 b) is also updated toindicate the position of platter 608 in the series. In some embodiments,scroll indicator 618 b is displayed in response to detecting scroll 616a, thereby indicating to the user that additional information can beviewed using rotational inputs through rotatable input mechanism 610 a.

The user again rotates 610 a (e.g., scroll 616 b; FIG. 6C). In responseto detecting scroll 616 b, device 600 ceases to display platter 606 anddisplays platter 608 at the former position of platter 606 (e.g., bytranslating 608 on-screen; FIG. 6D). In addition, platter 620 isdisplayed at the former position of platter 608 at a larger size and/orappearing closer to the user. In some embodiments, platter 620 displaysadditional information in this display position, such as the “leave now”text to let the user know that their commute home is predicted to bedisrupted by traffic in 40 minutes. Platter 622, associated with a newsapplication, is displayed at the former position of platter 620. Thescroll indicator (e.g., 618 c) is also updated to indicate the positionof platter 620 in the series.

The user again rotates 610 a (e.g., scroll 616 c; FIG. 6D). In responseto detecting scroll 616 c, device 600 ceases to display platter 608 anddisplays platter 620 at the former position of platter 608 (e.g., bytranslating 620 on-screen; FIG. 6E). In addition, platter 622 isdisplayed at the former position of platter 620 at a larger size and/orappearing closer to the user. In some embodiments, platter 622 displaysadditional information in this display position, such as the topheadline of the day. A partial view of platter 624, representingtomorrow's calendar events, is also displayed. The scroll indicator(e.g., 618 d) is also updated to indicate the position of platter 622 inthe series.

Platters 606, 608, 620, and 622 display sets of information obtainedfrom various applications that relate to temporal context(s) of thecurrent day. Platter 624 indicates to the user that information relatedto the next day is also displayable. The user rotates 610 a (e.g.,scroll 616 d; FIG. 6E), and in response to detecting scroll 616 d, thedisplay is updated as shown in FIG. 6F. In FIG. 6F, device 600 ceases todisplay platter 620, displays 622 in the former position of 620, anddisplays a full view of platter 624. Platter 624 is associated with thecalendar application and displays information obtained therefrom: anindication of the number of calendar events scheduled for tomorrow, andthe time of the first calendar event scheduled for tomorrow. A partialview of platter 626, representing tomorrow's predicted weather, is alsodisplayed. The scroll indicator (e.g., 618 e) is also updated toindicate the position of platter 624 in the series.

The user rotates 610 a (e.g., scroll 618 e; FIG. 6F) in order to viewall of platters 624 and 626. As shown in FIG. 6G, platter 626 displaystextual and graphical depictions of the weather conditions predicted fortomorrow, as well as the predicted high and low temperatures. The scrollindicator is also updated to indicate the position of platter 626 in theseries (e.g., 618 f). In some embodiments, as shown in FIG. 6G, platters624 and 626 do not display sets of information related to discretetemporal contexts of tomorrow, but rather display information related totomorrow generally, or related to multiple contexts of tomorrow. In someembodiments, platters associated with the current day display sets ofinformation related to discrete temporal contexts of the current day(e.g., single calendar events or weather notifications), whereasplatters associated with tomorrow display sets of information related tomultiple temporal contexts of tomorrow or the majority of tomorrow(e.g., a summary of multiple calendar events or a summary of the entireday's weather).

In order to return to the current time view, the user taps display 602(e.g., tap 628). In response to detecting tap 628, device 600 displaysceases to display platters 624 and 626 and displays platters 606 and 608(FIG. 6H). Indicator 618 a is also updated accordingly to reflect theposition of platter 606 along the series of displayable platters. Insome embodiments, the user returns to the user interface screen shown inFIG. 6H by scrolling in the opposite direction (e.g., by rotating 610 athrough rotational inputs in the opposite directions of scrolls 616 a,616 b, 616 c, 616 d, and 616 e).

In some embodiments, rather than scrolling the user interface screens byrotating 610 a, the user swipes display 602 to scroll the user interfacescreens and navigate through temporal context. For example, in responseto detecting swipe 630 a, device 600 translates platters 606 and 608,displays platter 620, and updates scroll indicator 618 b (FIG. 6I).FIGS. 61 and 6C demonstrate that swiping display 602 can be usedinterchangeably with rotating 610 a to scroll the user interface (e.g.,in either direction, as described herein).

FIG. 6J illustrates exemplary platters 606, 608, 634, 636, 638, 640,642, 644, 646, 648, 650, 652, 654, and 656 that can be displayed ondisplay 602. For example, platter 632 is associated with an activityapplication and displays a reminder to engage in a type of physicalactivity for a particular duration to meet an exercise goal; platter 634is associated with an alarm application and displays the time of anupcoming saved alarm; platter 636 is associated with a breathe reminderapplication and displays a reminder to breathe/meditate; platter 638 isassociated with a navigation application and displays an indication ofpredicted traffic conditions; platter 640 is associated with a newsapplication and displays a headline; platter 642 is associated with areminder application and displays a reminder and its designated time;platter 644 is associated with a stocks application and displays astock, its closing price, and recent stock activity; platter 646 isassociated with a photos application and displays a user photo; platter648 is associated with a photos application and displays a user photo;platter 650 is associated with a wallet application and displays apurchased movie ticket; platter 652 is associated with a sunrise/sunsetapplication and displays the time of today's sunset; platter 654 isassociated with a home application and displays an affordance foractivating a stored setting for one or more home devices (e.g., lights,curtains, music, door/window locks, etc.); and platter 656 is associatedwith a sunrise/sunset application and displays the time of tomorrow'ssunrise.

Device 600 can use a variety of selection criteria, alone or in anycombination, to select what set(s) of information are surfaced to theuser in a platter, as illustrated by FIG. 6J. In some embodiments, theset of selection criteria includes temporal context of the set ofinformation. For example, a calendar event (e.g., as shown in platter608), weather notification (e.g., as shown in platter 606), reminder(e.g., as shown in platter 642), alarm, (e.g., as shown in platter 634),photo (e.g., a photo taken on a previous date on the current day of themonth or year, as shown in platter 646), sunset/sunrise time (e.g., asshown in platters 652 and 656), or closing stock price (e.g., as shownin platter 644) can be selected for display because they relate to acurrent or upcoming time (e.g., in the current day).

In some embodiments, the selection criteria includes temporal context ofthe set of information and one or more additional selection criteria. Insome embodiments, whether a set of information obtained from anapplication is displayed in a platter is determined based on dataobtained from multiple applications. For example, information can besurfaced to the user because it relates to a particular application anda set of selection criteria are met, determined based on data fromanother application; an activity platter can be selected for displaybecause the displayed reminder relates to the activity application(e.g., based on data related to the user's daily activity goal) and aset of criteria are met based on data from the calendar application(e.g., a predetermined amount of time until the next scheduled calendarevent). In some embodiments, the selection criteria includes proximityto a second device (e.g., device belonging to a contact).

In some embodiments, the selection criteria can include time until thenext scheduled calendar event. In this example, the temporal contextrelates to a time of day when device 600 surfaces this set ofinformation to the user. If the user has sufficient time betweenscheduled events, the device can surface a reminder from the activityapplication (e.g., platter 632) because the user has time for a workoutor other activity. In some embodiments, the selection criteria caninclude a number of calendar events scheduled for the current day.Platter 636 can be displayed because the set of information relates to adifferent temporal context and the breathe reminder application. In thisinstance, device 600 can surface a breathe reminder to the user becauseseveral consecutive calendar events have been concluded, and thus theuser may wish to take a minute to breathe and recover. In someembodiments, the selection criteria can include the application fromwhich the information is obtained. For example, device 600 can select anactivity reminder (e.g., as shown in platter 632) because an activitygoal for the day is still outstanding, or device 600 can select abreathe reminder because the day's scheduled calendar events haveconcluded (as described above). These functionalities allow the deviceto surface sets of information from various applications at times whenthe user may wish to use these functionalities, rather than at apredetermined time designated by the user or an external data source.

In some embodiments, the selection criteria can include locationinformation. For example, platter 650 can be displayed because the setof information (a movie ticket) relates to a temporal context (upcomingshowtime during the current day; 7:15 pm in this example) and location(e.g., device 600 is close to the movie theater). Platter 638 can bedisplayed because the set of information (traffic conditions) relates toa temporal context (a time of day when the user typically begins theircommute, or the time of day most common for commuting generally) andlocation (e.g., device 600 is close to the work, not home, and thepredicted traffic is between work and home). Platter 648 can bedisplayed because it relates to location (e.g., device 600 is near thelocation where a previous user photo was taken). In some embodiments,device 600 obtains data representing its current location from alocation sensor associated with device 600 (e.g., GPS sensor 532 ofdevice 600, or GPS module 135 of device 100 paired or coupled viawireless communication with device 600). In some embodiments, thelocation information is obtained from another application, such as acalendar application. For example, the device can display a platter witha set of information (e.g., weather conditions) from a weatherapplication pertaining to the location of an upcoming calendar event. Ifthe user is in San Francisco, but has a calendar event or plane ticketto New York later in the day, the device can display a platter withweather information related to New York.

In some embodiments, the selection criteria can include one or moreprevious user inputs. For example, platter 654 can be displayed prior toa time of day when the user has previously used the home application(e.g., at bedtime). Platter 638 can be displayed prior to a time of daywhen the user has previously started their commute. In this example, theuser input can be a movement of the device corresponding to the usertraveling home, e.g., one or more inputs received from GPS sensor 532,accelerometer 534, directional sensor 540 (e.g., compass), gyroscope536, motion sensor 538, and/or a combination thereof.

In addition to displaying sets of information related to particulartemporal contexts of the current day, these context-specific userinterfaces can also display sets of information related to the currentday, e.g., independent of a specific temporal context, or related to amajority of the current day. These “all-day” events are also accessibleby scrolling the user interface. As shown in FIG. 6K, when platters 606and 608 are displayed (e.g., the current time view), the user rotates610 a in the direction opposite scroll 616 a (e.g., scroll 658 a).

In response to detecting scroll 658 a, the device 600 displays thescreen shown in FIG. 6L. Platter 606 is translated on-screen, scrollindicator 618 b is updated, and “all-day” platter 660 is displayed.Platter 660 is associated with a weather application and displays a setof information related to the entire current day (e.g., predictedweather conditions and high and low temperatures forecasted for thecurrent day).

Later in the day, display 602 shows platters 620 and 622 (FIG. 6M).Current time indicator 604 has been updated in FIG. 6M to reflect thecurrent time. Compared to the screen shown in FIG. 6K, the screen shownin FIG. 6M shows different events because the current time is later(e.g., 1:00 as compared to 10:09). Since the sets of informationdisplayed in platters 620 and 622 are now most current at 1:00, theseplatters are displayed instead of platters 606 and 608. Thus, differentplatters can be displayed to the user at different times of day. In someembodiments, platters displaying sets of information related to pasttimes in the current day cease to display on display 602. In someembodiments, one platter corresponding to the most recent past event isdisplayed.

The user scrolls the user interface by rotating 610 a via scroll 658 b.In response to detecting scroll 658 b, the device displays the screenshown in FIG. 6N. As shown in FIG. 6N, device 600 displays platters 620and 660. Thus, the user can access information from “all-day” platters(e.g., 660) at any time in the current day, while event-specificplatters (e.g., 606 or 620) can be displayed based on specific temporalcontexts within the current day. In summary, scrolling the userinterface screen (e.g., by rotating 610 a and/or swiping) in onedirection reveals future event platters related to the current dayand/or the next day (see FIGS. 6B-6I), and scrolling the user interfacescreen (e.g., by rotating 610 a and/or swiping) in the other directionreveals “all-day” event platters related to the current day (see FIGS.6K-6N).

In some embodiments, one or more “all-day” event platters can beselected (e.g., by the device) for display based on one or moreselection criteria, e.g., as described above. For example, platter 660can be surfaced to the user because it relates to a location (e.g.,all-day weather conditions at the current location of the device) and/orthe application from which the set(s) of information are obtained (e.g.,showing an all-day weather platter).

In some embodiments, in addition to or in place of displaying sets ofinformation obtained from the corresponding application, event andall-day platters can also serve as affordances to launch thecorresponding application. In FIG. 6O, the user contacts displayedplatter 606 with tap 662 a. In response to detecting tap 662 a, device600 ceases to display platter 606 and displays a user interface screenfrom the corresponding application (in this example, a weatherapplication; FIG. 6P).

The user can also select displayed complications to launch applications.In FIG. 6Q, in order to launch a personal assistant application, theuser contacts displayed complication 614 with tap 662 b. In response todetecting tap 662 b, device 600 ceases to display complication 614 anddisplays a user interface screen from the corresponding application(FIG. 6R). In some embodiments, complication 614 is “pinned” to the userinterface screen such that it remains displayed (and optionally in afixed position) while the event and/or all-day platters are scrolled(see FIGS. 6B-6N). This allows the user to use the complication at anytime, regardless of which event platters are shown. In some embodiments,the personal assistant application is launched to reflect a context of acurrently running application, or the most recently launchedapplication.

The user may wish to edit the application represented by complication614 and/or other aspects of the user interface, such as colors, densityof displayed information, and so forth. Additional descriptions ofediting and/or selecting context-specific user interfaces andsub-components thereof may be found in International Patent ApplicationSerial No. PCT/US2015/034607, titled “Context-Specific User Interfaces,”filed Jun. 7, 2015, published as WIPO Publication No. WO/2016/022205,which is incorporated by reference herein in its entirety.

In FIG. 6S, the user accesses an edit mode of device 600 through press664, which in some embodiments can be a press having a duration longerthan a predetermined duration (e.g., a “long press” input) or a contacthaving a characteristic intensity above an intensity threshold. In thisexample, in response to detecting press 664, device 600 enters acontext-specific user interface selection mode and visuallydistinguishes the user interface screen to indicate the selection mode(FIG. 6T). Device 600 alerts to the user that it has entered into theselection mode by displaying smaller representation 666 of the userinterface screen, name 668 corresponding to a name of the type ofcontext-specific user interface currently selected, partial view 670 ofan adjacent, stored context-specific user interface (which the usercould select by swiping to view the full interface and tapping to selectit), and edit affordance 672. In order to edit the user interface, theuser contacts edit affordance 672 via tap 674.

In response to detecting tap 674, the device enters edit mode andvisually distinguishes one or more aspects of the user interface forediting (FIG. 6U). In this example, complication 614 is selected forediting. Device 600 informs the user that complication 614 is selectedfor editing by visually distinguishing complication 614 via displayingoutline 676 a around complication 614 and indicator 676 b, whichindicates the application represented by the complication (in thisexample, the personal assistant application). Device 600 also displaysscroll indicator 680 a, which informs the user that additionalapplications can be selected by scrolling and indicates the position ofthe personal assistant application along the series of displayableapplication options. Device 600 also displays paging affordance 678,which indicates that two options for editing different aspects of theuser interface can be selected (e.g., by swiping). In this example, theoptions include the application represented by complication 614 and oneor more colors associated with the user interface (e.g., one or morecolors of the current time indicator and/or displayed platters).

In response to detecting scroll 682 (a rotation of 610 a), device 600replaces complication 614 with complication 684, which represents aremote application (FIG. 6V). In addition, indicator 676 b is updated toindicate the remote application, and scroll indicator 680 b is updatedto reflect the position of the remote application along the series ofselectable application options. In some embodiments, in response todetecting one or more additional inputs, device 600 displays a userinterface screen based on the display 602 shown in FIG. 6V (e.g., adepression of 610 a followed by a tap on the displayed user interface inselection mode). In some embodiments, device 600 stores the edited userinterface in memory (e.g., in memory 518 and/or memory 102 of device 100paired or coupled via wireless communication with device 600). In someembodiments, the edited user interface screen can be subsequentlyselected in selection mode, e.g., as described in International PatentApplication Serial No. PCT/US2015/034607, titled “Context-Specific UserInterfaces,” filed Jun. 7, 2015, published as WIPO Publication No.WO/2016/022205 (see, e.g., display 1322 in FIG. 13 ).

FIGS. 7A-7E show a flow diagram illustrating process 700 for providingcontext-specific user interfaces. In some embodiments, process 700 canbe performed at an electronic device with a touch-sensitive display, oneor more processors, and memory, such as device 100 (FIG. 1A), 300 (FIG.3 ), 500 (FIGS. 5A-5H), or 600 (FIGS. 6A-6V). Some operations in process700 can be combined, the order of some operations may be changed, andsome operations can be omitted.

In FIG. 7A, at block 702, the device displays a user interface screencomprising a current time indicator and a first platter at a firstposition (e.g., on the display). As shown in block 704, the firstplatter is associated with a first application and displays a first setof information obtained from the first application (see, e.g., platter608 in FIG. 6C, which is associated with a calendar application anddisplays the time, name, and location of a scheduled calendar event). Asshown in block 706, the first set of information relates to a firsttemporal context of the current day (e.g., the time of the calendarevent). As described above, a “temporal context” can relate to a timeattached to a set of information by the user, a time attached to a setof information by an external data source, or a time attached to a setof information by an electronic device of the present disclosure.

At block 708, the device detects a user input. In some embodiments,detecting the user input comprises detecting a rotation of a rotatableinput mechanism (e.g., scroll 616 b in FIG. 6C). In some embodiments,detecting the user input comprises detecting a swipe on atouch-sensitive display (e.g., swipe 630 a in FIG. 6H).

At block 710, in response to detecting the user input, the devicedisplays the first platter at a second position different from the firstposition (cf. the position of platter 608 in FIGS. 6C and 6D). In someembodiments, the first platter is displayed at the second position at alarger size (e.g., appearing larger and/or closer to the viewer) thanwhen displayed at the first position (cf. platter 608 in FIGS. 6C and6D). In some embodiments, the first platter displays more informationwhen displayed at the second position than when displayed at the firstposition (cf. platter 608 in FIGS. 6C and 6D).

At block 712, in response to detecting the user input, the devicedisplays a second platter at the first position (e.g., platter 620 inFIG. 6D). As shown in block 714, the second platter is associated with asecond application and displays a second set of information obtainedfrom the second application (see, e.g., platter 620 in FIG. 6D, which isassociated with a navigation application and displays the time ofpredicted traffic conditions). As shown in block 716, the second set ofinformation relates to a second temporal context of the current day. Insome embodiments, the first and the second applications are different.For example, in some embodiments, the first and the second applicationsare each an independently selected application selected from: weather,calendar, activity, breathe reminder, photos, reminder, and stocksapplications. In some embodiments, the first and the second temporalcontexts are different. In some embodiments, the first and the secondtemporal contexts are the same. Displaying sets of information obtainedfrom different applications, throughout temporal contexts in the currentday, provides the user with relevant application data (and optionallyaffordances for launching applications) from multiple applicationswithout necessitating the display of multiple, dedicated applicationwidgets (each dedicated to, and showing information obtained from, asingle application). Providing additional control options withoutcluttering the user interface with additional displayed controls (e.g.,dedicated application widgets) enhances the operability of the deviceand makes the user-device interface more efficient (e.g., by helping theuser to provide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In FIG. 7B, at block 718, the device optionally detects a second userinput (e.g., after displaying the second platter). In some embodiments,detecting the second user input comprises detecting a rotation of arotatable input mechanism (e.g., scroll 616 c in FIG. 6D). In someembodiments, detecting the second user input comprises detecting a swipeon a touch-sensitive display (e.g., swipe 630 a in FIG. 6H).

At block 720, in response to detecting the second user input, the deviceoptionally displays the second platter at a position different from thefirst position on the display (see platter 620 in FIG. 6E). As shown inblock 722, in some embodiments, the device optionally ceases to displaythe first platter (see disappearance of platter 608 from FIG. 6D to FIG.6E) before displaying the second platter (e.g., at the second position).

At block 724, in response to detecting the second user input, the deviceoptionally displays a third platter at the first position (see platter622 in FIG. 6E). In some embodiments, as shown in block 726, the thirdplatter is associated with a third application and displays a third setof information obtained from the third application. The thirdapplication is different from the first and the second applications, andthe third set of information relates to a third temporal context of thecurrent day. In some embodiments, as shown in block 728, the thirdplatter is associated with the first application and displays a thirdset of information obtained from the first application. The first andthe third sets of information are different, the third set ofinformation relates to a third temporal context of the current day, andthe first and the third temporal contexts are different. This enablesthe device to display different sets of application information, each ofwhich may be relevant at a different time of day, without requiring theuser to launch the application(s) in order to access the multiple setsof information. Performing an operation when a set of conditions (e.g.,relevant temporal context and/or particular application) has been metwithout requiring further user input enhances the operability of thedevice and makes the user-device interface more efficient (e.g., byhelping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

At block 730, in response to detecting the second user input, the deviceoptionally displays the first platter at a third position different fromthe first and the second positions on the display (see the positions ofplatter 620 in FIGS. 6C, 6D, and 6E).

In FIG. 7C, at block 732, the device optionally displays on the displayan indicator of position along a series of positions, e.g., in responseto detecting the first user input (see indicator 618 b in FIG. 6C). Theindicator of position along a series of positions indicates a positionof the second platter along a series of displayable platters.

At block 734, in response to detecting the second user input, the deviceoptionally updates the indicator of position to indicate a position ofthe third platter along the series of displayable platters (cf. scrollindicators 618 a-618 f in FIGS. 6B-6G). Displaying an updating scrollindicator that indicates a position of a currently selected option alonga series of selectable options provides feedback to the user that thereceived user input (e.g., rotating 610 a) controls selection of thedisplayed option while helping the user to navigate through the entireseries of options (as well as indicating to the user that additionaloptions are displayable). Providing improved feedback enhances theoperability of the device and makes the user-device interface moreefficient (e.g., by helping the user to provide proper inputs andreducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

At block 736, the device optionally detects a contact (e.g., on thetouch-sensitive display) after displaying the second platter. In someembodiments, the contact is at a position on the display different fromthe positions of the displayed platter(s) and/or complication(s). Insome embodiments, the contact is a tap gesture (e.g., tap 628 in FIG.6G).

At block 738, in response to detecting the contact, the deviceoptionally ceases to display the second platter.

At block 740, in response to detecting the contact, the deviceoptionally displays the first platter at the first position (see platter608 in FIG. 6H).

At block 742, the device optionally detects a third user input, e.g.,after displaying the second platter. In some embodiments, detecting thethird user input comprises detecting a rotation of a rotatable inputmechanism (e.g., scroll 616 d or 616 e in FIGS. 6E & 6F). In someembodiments, detecting the third user input comprises detecting a swipeon a touch-sensitive display (e.g., swipe 630 a in FIG. 6H).

In FIG. 7D, at block 744, the device optionally displays a fourthplatter on the display in response to detecting the third user input. Insome embodiments, as shown in block 746, the fourth platter isassociated with a fourth application and displays a fourth set ofinformation obtained from the fourth application, and the fourthapplication is different from the first and the second applications. Insome embodiments, as shown in block 748, the fourth platter isassociated with the first application and displays a fourth set ofinformation obtained from the first application, and the first and thefourth sets of information are different. The fourth set of informationrelates to a temporal context of a future day (e.g., tomorrow), such asthe sets of information shown by platters 624 and 626 in FIG. 6G.

At block 750, the device optionally detects a user input correspondingto a selection of the first platter. For example, in some embodiments,detecting the user input comprises detecting a contact on thetouch-sensitive display at (e.g., on or near) the displayed firstplatter (see tap 662 a in FIG. 6O).

At block 752, the device optionally launches the first application inresponse to detecting the user input corresponding to a selection of thefirst platter. In some embodiments, launching the first applicationcomprises ceasing to display the first user interface screen anddisplaying a second user interface screen corresponding to theapplication (see FIG. 6P).

At block 754, the device optionally displays an affordance thatrepresents an application (see complication 614 in FIG. 6Q). In someembodiments, the affordance is displayed at a position different fromthe first and the second positions on the display. In some embodiments,the affordance represents an application that is different from thefirst and the second applications. In some embodiments, the affordancerepresents the first or the second application. In some embodiments, theaffordance comprises a set of information obtained from the applicationit represents. In some embodiments, the set of information is updated inaccordance with data (e.g., updated data) obtained from the applicationit represents. In some embodiments, the affordance is displayed in thesame position on the display before and after updating the set ofinformation.

At block 756, the device optionally detects a user input correspondingto a selection of the affordance (e.g., a tap on or near the displayedaffordance, such as tap 662 b in FIG. 6Q).

At block 758, the device optionally launches the application representedby the affordance in response to detecting the user input correspondingto a selection of the affordance. In some embodiments, launching theapplication comprises ceasing to display the first user interface screenand displaying a second user interface screen corresponding to theapplication (see FIG. 6R).

In FIG. 7E, at block 760, the device optionally detects a user inputcorresponding to a request to enter an affordance edit mode of theelectronic device, e.g., before launching the application. In someembodiments, the user input is a press having a duration longer than apredetermined duration (e.g., a “long press” input). In someembodiments, the device determines whether the detected press has aduration longer than a predetermined duration and, in accordance with adetermination that the detected press has a duration longer than thepredetermined duration, enters the affordance edit mode. In someembodiments, the user input is a contact having a characteristicintensity above an intensity threshold. In some embodiments, the devicedetermines whether the detected contact has a characteristic intensityabove a predetermined duration and, in accordance with a determinationthat the detected press has a characteristic intensity above thepredetermined duration, enters the affordance edit mode.

At block 762, the device optionally enters an affordance edit mode inresponse to detecting the user input corresponding to a request to enteran affordance edit mode. In some embodiments, as shown at block 764,entering the affordance edit mode comprises displaying an edit modeaffordance on the touch-sensitive display (e.g., affordance 672 in FIG.6T) and, as shown at block 766, detecting a user input corresponding toa selection of the edit mode affordance (e.g., tap 674 in FIG. 6T).

At block 768, the device optionally visually distinguishes theaffordance to indicate the affordance edit mode in response to detectingthe user input corresponding to a request to enter an affordance editmode. For example, the device can display an outline around theaffordance, animate an outline around the affordance, animate theaffordance (e.g., to flash or expand and contact) change a color of theaffordance, and/or display an additional indicator to visuallydistinguish the affordance (see outline 676 a and indicator 676 b inFIG. 6U). Visually distinguishing the affordance to indicate edit modeprovides improved feedback to the user both that the device has entereda different mode of functionality (for example, tapping the affordancecan lead to launch of the corresponding application during a mode otherthan edit mode but select the affordance for editing during edit mode)and that the distinguished affordance is the aspect of the interfacecurrently selected for editing. Providing improved feedback enhances theoperability of the device and makes the user-device interface moreefficient (e.g., by helping the user to provide proper inputs andreducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently. In some embodiments, as shown at block 770, visuallydistinguishing the affordance to indicate the affordance edit modefurther comprises displaying an indicator of position along a series ofpositions, the indicator indicating a first position along the series(e.g., scroll indicator 680 a in FIG. 6U).

At block 772, the device optionally detects a second user inputcorresponding to a request to change the application represented by theaffordance. For example, in some embodiments, detecting the second userinput comprises detecting a rotation of a rotatable input mechanism(e.g., scroll 682 received by rotatable input mechanism 610 a in FIG.6U).

At block 774, the device optionally updates the affordance to representa different application in response to detecting the second user inputcorresponding to a request to change the application represented by theaffordance (see affordance 784 and indicator 676 b in FIG. 6V). In someembodiments, as shown at block 776, the device updates the indicator ofposition to indicate a second position along the series, where theindicator of position along a series of positions indicates a positionof a currently selected option for the application represented by theaffordance along a series of selectable options for the applicationrepresented by the affordance (see scroll indicator 680 b in FIG. 6V).

It should be understood that the particular order in which theoperations in FIGS. 7A-7E have been described is merely exemplary and isnot intended to indicate that the described order is the only order inwhich the operations could be performed. One of ordinary skill in theart would recognize various ways to reorder the operations describedherein.

Note that details of the processes described above with respect toprocess 700 (e.g., FIGS. 7A-7E) are also applicable in an analogousmanner to the methods described elsewhere in this application. Forexample, other methods described in this application may include one ormore of the characteristics of process 700. For example, one or more ofthe steps of process 700 can be combined with one or more of the stepsof process 800, as described below. For brevity, these details are notrepeated below.

FIGS. 8A-8G show a flow diagram illustrating process 800 for providingcontext-specific user interfaces. In some embodiments, process 800 canbe performed at an electronic device with a touch-sensitive display, oneor more processors, and memory, such as device 100 (FIG. 1A), 300 (FIG.3 ), 500 (FIGS. 5A-5H), or 600 (FIGS. 6A-6V). Some operations in process800 can be combined, the order of some operations may be changed, andsome operations can be omitted.

In FIG. 8A, at block 802, the device displays at a first time a userinterface screen comprising a current time indicator, a first platter ata first position (e.g., on the display), and an affordance at a secondposition (e.g., on the display). The current time indicator reflects thefirst time of the current day (e.g., indicator 604 in FIG. 6K). As shownin block 804, the first platter is associated with a first applicationand displays a first set of information obtained from the firstapplication (see, e.g., platter 606 in FIG. 6K, which is associated witha weather application and displays the time and a description of apredicted change in weather or inclement weather conditions). As shownin block 806, the first set of information relates to a first temporalcontext of the current day (e.g., the time of the predicted change inweather or inclement weather conditions). As shown in block 808, theaffordance represents an application (e.g., affordance 614 in FIG. 6K,which represents a personal assistant application). In some embodiments,the affordance comprises a set of information obtained from theapplication it represents. In some embodiments, the set of informationis updated in accordance with data (e.g., updated data) obtained fromthe application it represents. In some embodiments, the affordance isdisplayed in the same position on the display before and after updatingthe set of information.

At block 810, the device detects a first user input corresponding to arequest to scroll the first user interface screen. In some embodiments,the first user input comprises a rotation of a rotatable input mechanism(e.g., scroll 658 a received at rotatable input mechanism 610 a shown inFIG. 6K). In some embodiments, the first user input comprises a swipe ona touch-sensitive display.

At block 812, in response to detecting the first user input, the devicemaintains display of the affordance at the second position (cf.affordance 614 in FIG. 6K and FIG. 6L).

In FIG. 8B, at block 814, in response to detecting the first user input,the device displays a second platter at the first position. In someembodiments, as shown in block 816, the second platter is associatedwith a second application (e.g., platter 660 associated with a weatherapplication as shown in FIG. 6L) and displays a second set ofinformation obtained from the second application (e.g., weatherconditions and/or high and low temperatures forecasted for the currentday, as shown in platter 660 in FIG. 6L). In some embodiments, the firstand the second applications are the same. In some embodiments, the firstand the second applications are different. In some embodiments, as shownin block 818, the second set of information relates to the current day(e.g., to a temporal context of the current day broader than the firsttemporal context).

At block 820, the device displays at a second time (e.g., a differenttime of day than the first time), a second user interface screencomprising the current time indicator, a third platter at the firstposition on the display (e.g., 620 in FIG. 6M), and the affordance atthe second position on the display (e.g., 614 in FIG. 6M). As shown inblock 822, the third platter is associated with a third application(e.g., a navigation application, as shown in FIG. 6M) and displays athird set of information obtained from the third application (e.g., timeof a predicted change in traffic, such as traffic along the user's routehome). As shown in block 824, the third set of information relates to athird temporal context of the current day. As shown in block 826, thecurrent time indicator reflects the second time of the current day(e.g., indicator 604 in FIG. 6M). In some embodiments, the first and thethird applications are the same. In some embodiments, the first and thethird applications are different. Displaying sets of informationobtained from different applications, some of which change throughoutthe day (e.g., based on temporal context) and some of which are constantthroughout the day, provides the user with relevant application data(and optionally affordances for launching applications) from a varietyof applications without necessitating the display of multiple, dedicatedapplication widgets (each dedicated to, and showing information obtainedfrom, a single application). Providing additional control optionswithout cluttering the user interface with additional displayed controls(e.g., dedicated application widgets) enhances the operability of thedevice and makes the user-device interface more efficient (e.g., byhelping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

At block 828, the device detects a second user input corresponding to arequest to scroll the second user interface screen. In some embodiments,the second user input comprises a rotation of a rotatable inputmechanism (e.g., scroll 658 b received at rotatable input mechanism 610a shown in FIG. 6M). In some embodiments, the second user inputcomprises a swipe on a touch-sensitive display.

In FIG. 8C, at block 830, in response to detecting the second userinput, the device maintains display of the affordance at the secondposition (cf. affordance 614 in FIG. 6M and FIG. 6N).

At block 832, in response to detecting the second user input, the devicedisplays the second platter at the first position (e.g., platter 660 inFIG. 6N).

At block 834, the device optionally detects a third user inputcorresponding to a request to scroll the second user interface screen ina second scroll direction different from the first scroll direction. Insome embodiments, the third user input comprises a rotation of arotatable input mechanism (e.g., scroll 616 a received at rotatableinput mechanism 610 a shown in FIG. 6B, which is in an oppositedirection as compared to scroll 658 a). In some embodiments, the thirduser input comprises a swipe on a touch-sensitive display (e.g., in anopposite swipe direction).

At block 836, the device optionally maintains display of the affordanceat the second position in response to detecting the third user input.

At block 838, the device optionally displays a fourth platter at thefirst position on the display in response to detecting the third userinput. As shown in block 840, the fourth platter is associated with afourth application and displays a fourth set of information obtainedfrom the fourth application. In some embodiments, the first and thefourth applications are the same. In some embodiments, the first and thefourth applications are different. As shown in block 842, the fourth setof information relates to a fourth temporal context of the current day,and the fourth temporal context is different from the third temporalcontext. In some embodiments, the fourth temporal context is later thanthe third temporal context in the current day.

In FIG. 8D, at block 844, the device optionally displays on the displayan indicator of position along a series of positions in response todetecting the second user input. The indicator of position along aseries of positions indicates a position of the second platter along aseries of displayable platters (e.g., scroll indicator 618 b in FIG.6N).

At block 846, the device optionally updates the indicator of position toindicate a position of the fourth platter along the series ofdisplayable platters in response to detecting the third user input.Displaying an updating scroll indicator that indicates a position of acurrently displayed platter along a series of displayable plattersprovides feedback to the user that the received user input (e.g., scroll616 a) controls selection of the displayed platter(s) while helping theuser to navigate through the entire series of platter options (as wellas indicating to the user that additional platters are displayable).Providing improved feedback enhances the operability of the device andmakes the user-device interface more efficient (e.g., by helping theuser to provide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

At block 848, the device optionally detects a fourth user inputcorresponding to a request to scroll the second user interface screen inthe second scroll direction (e.g., scrolls 616 d and 616 e in FIGS. 6Eand 6F).

At block 850, the device optionally maintains display of the affordanceat the second position in response to detecting the fourth user input.

At block 852, the device optionally displays a fifth platter at thefirst position on the display in response to detecting the fourth userinput (e.g., platter 624 in FIG. 6F). As shown in block 854, the fifthplatter is associated with a fifth application and displays a fifth setof information obtained from the fifth application. In some embodiments,the first and the fifth applications are the same. In some embodiments,the first and the fifth applications are different. As shown in block856, the fifth set of information relates to a temporal context of thenext day (e.g., a number of calendar events, as shown in platter 624 inFIG. 6G, or tomorrow's predicted weather, as shown in platter 626 inFIG. 6G).

In FIG. 8E, at block 858, the device optionally detects a fifth userinput. In some embodiments, the fifth user input comprises a contact onthe touch-sensitive display (e.g., tap 628 in FIG. 6G). In someembodiments, the fifth user input comprises a rotation of a rotatableinput mechanism.

At block 860, the device optionally maintains display of the affordanceat the second position in response to detecting the fifth user input.

At block 862, the device optionally ceases to display the fourth platterin response to detecting the fifth user input.

At block 864, the device optionally displays the third platter at thefirst position in response to detecting the fifth user input.

At block 866, the first and the third sets of information are selectedfor display based at least in part on a set of one or more selectioncriteria. For example, as described in reference to FIG. 6J, the set ofone or more selection criteria can comprise a temporal context of thecurrent day (e.g., the time of a calendar event shown in platter 606 orthe showtime associated with a movie ticket shown in platter 650 in FIG.6J). In some embodiments, the set of one or more selection criteria cancomprise a temporal context of the current day and one or more selectioncriteria selected from: location (e.g., the photo represented in platter648 in FIG. 6J), the application from which the first or the third setof information is obtained (e.g., surfacing traffic conditions from anavigation application to the user at the time of the user's commutehome, as shown in platter 638 in FIG. 6J), a number of calendar eventsscheduled for the current day (e.g., surfacing a breathe reminder to theuser after consecutive calendar events, as shown in platter 636 in FIG.6J), time until the next scheduled calendar event (e.g., surfacing anactivity reminder to the user when the user has time for a workoutbefore the next scheduled calendar event, as shown in platter 632 inFIG. 6J), and one or more previous user inputs (e.g., surfacing aplatter associated with a home application at a time when the user haspreviously launched the home application, as shown in platter 654 inFIG. 6J). Optionally, as shown in block 868, if the set of one or moreselection criteria comprises proximity to the current location of theelectronic device (e.g., the photo shown in platter 648, or the reminderto leave work when the device detects that it is near the user'sdesignated workplace shown in platter 638 in FIG. 6J), the deviceobtains its current location from a location sensor associated with theelectronic device (e.g., GPS sensor 532 of device 600, or GPS module 135of device 100 paired or coupled via wireless communication with device600). Using, via the device, the set of one or more selection criteriato automatically generate and display a platter provides information tothe user that is relevant to the current time (e.g., providing the userwith a workout or breathe reminder when their schedule allows, asdetermined in accordance with data from the calendar application)without requiring a user input (e.g., to set such a reminder inadvance). Performing operations when a set of conditions has been metwithout requiring further user input enhances the operability of thedevice and makes the user-device interface more efficient (e.g., byhelping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently. Using selection criteriafurther allows the device to display different platters at differenttimes of day from a variety of applications without necessitating thedisplay of multiple, dedicated application widgets (each dedicated to,and showing information obtained from, a single application). Providingadditional control options without cluttering the user interface withadditional displayed controls (e.g., dedicated application widgets)enhances the operability of the device and makes the user-deviceinterface more efficient (e.g., by helping the user to provide properinputs and reducing user mistakes when operating/interacting with thedevice) which, additionally, reduces power usage and improves batterylife of the device by enabling the user to use the device more quicklyand efficiently.

At block 870, the device optionally selects the second set ofinformation for display based at least in part on a second set of one ormore selection criteria. For example, the second set of selectioncriteria can include one or more selection criteria selected from:location and the application from which the second set of information isobtained. In some embodiments, the second set of one or more selectioncriteria does not comprise a temporal context of the current day. Insome embodiments, the second set of information relates to a majority oftime within the current day (e.g., the weather conditions and high/lowtemperatures shown in platter 660 in FIGS. 6L and 6N). In someembodiments, the second set of information relates to a temporal contextof the current day that is broader than the first and the third temporalcontexts (e.g., the weather conditions and high/low temperatures shownin platter 660 in FIG. 6L, as compared to the weather alert shown inplatter 606 in FIG. 6K). Optionally, as shown in block 872, if thesecond set of one or more selection criteria comprises proximity to thecurrent location of the electronic device, the device obtains itscurrent location from a location sensor associated with the electronicdevice (e.g., GPS sensor 532 of device 600, or GPS module 135 of device100 paired or coupled via wireless communication with device 600).

In FIG. 8F, at block 874, the device optionally detects a user inputcorresponding to a selection of the second platter. For example,detecting the user input can comprise detecting a contact at (e.g., onor near) the displayed second platter, such as tap 662 a on platter 606in FIG. 6O.

At block 876, the device optionally launches the second application inresponse to detecting the user input corresponding to a selection of thesecond platter. In some embodiments, launching the second applicationcomprises ceasing to display the first or second user interface screenand displaying a third user interface screen corresponding to the secondapplication (see FIG. 6P).

At block 878, the device optionally detects a user input correspondingto a selection of the affordance. For example, detecting the user inputcan comprise detecting a contact at (e.g., on or near) the displayedaffordance, such as tap 662 b on complication 614 in FIG. 6Q.

At block 880, the device optionally launches the second application inresponse to detecting the user input corresponding to a selection of theaffordance. In some embodiments, launching the application comprisesceasing to display the first or second user interface screen anddisplaying a fourth user interface screen corresponding to theapplication (see FIG. 6R).

At block 882, the device optionally detects a user input correspondingto a request to enter an affordance edit mode. In some embodiments, theuser input is a press having a duration longer than a predeterminedduration (e.g., a “long press” input). In some embodiments, the devicedetermines whether the detected press has a duration longer than apredetermined duration and, in accordance with a determination that thedetected press has a duration longer than the predetermined duration,enters the affordance edit mode. In some embodiments, the user input isa contact having a characteristic intensity above an intensitythreshold. In some embodiments, the device determines whether thedetected contact has a characteristic intensity above a predeterminedduration and, in accordance with a determination that the detected presshas a characteristic intensity above the predetermined duration, entersthe affordance edit mode.

At block 884, the device optionally enters an affordance edit mode inresponse to detecting the user input corresponding to a request to enteran affordance edit mode. In some embodiments, as shown at block 886,entering the affordance edit mode comprises displaying an edit modeaffordance on the touch-sensitive display (e.g., affordance 672 in FIG.6T) and, as shown at block 888, detecting a user input corresponding toa selection of the edit mode affordance (e.g., tap 674 in FIG. 6T).

In FIG. 8G, at block 890, the device optionally visually distinguishesthe affordance to indicate the affordance edit mode in response todetecting the user input corresponding to a request to enter anaffordance edit mode. For example, the device can display an outlinearound the affordance, animate an outline around the affordance, animatethe affordance (e.g., to flash or expand and contact) change a color ofthe affordance, and/or display an additional indicator to visuallydistinguish the affordance (see outline 676 a and indicator 676 b inFIG. 6U). Visually distinguishing the affordance to indicate edit modeprovides improved feedback to the user both that the device has entereda different mode of functionality (for example, tapping the affordancecan lead to launch of the corresponding application under normalfunctioning but select the affordance for editing during edit mode) andthat the distinguished affordance is the aspect of the interfacecurrently selected for editing. Providing improved feedback enhances theoperability of the device and makes the user-device interface moreefficient (e.g., by helping the user to provide proper inputs andreducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently. In some embodiments, as shown at block 892, visuallydistinguishing the affordance to indicate the affordance edit modefurther comprises displaying an indicator of position along a series ofpositions, the indicator indicating a first position along the series(e.g., scroll indicator 680 a in FIG. 6U). In some embodiments, as shownat block 894, the device updates the indicator of position to indicate aposition of a currently selected option for the application representedby the affordance along a series of selectable options for theapplication represented by the affordance (see scroll indicator 680 b inFIG. 6V).

At block 896, the device optionally detects a second user inputcorresponding to a request to change the application represented by theaffordance. For example, in some embodiments, detecting the second userinput comprises detecting a rotation of a rotatable input mechanism(e.g., scroll 682 received by rotatable input mechanism 610 a in FIG.6U).

At block 898, the device optionally updates the affordance to representa different application in response to detecting the second user inputcorresponding to a request to change the application represented by theaffordance (see affordance 784 and indicator 676 b in FIG. 6V).

Note that details of the processes described above with respect toprocess 800 (e.g., FIGS. 8A-8G) are also applicable in an analogousmanner to the methods described elsewhere in this application. Forexample, other methods described in this application may include one ormore of the characteristics of process 800. For example, one or more ofthe steps of process 800 can be combined with one or more of the stepsof process 700, as described above. For brevity, these details are notrepeated below.

FIGS. 9A-9L show exemplary context-specific user interfaces that may beoperated on device 900. Device 900 may be device 100, 300, or 500 insome embodiments. The electronic device has a display 902 (e.g., 504).In some embodiments, display 902 is a touch-sensitive display. In someembodiments, device 900 includes rotatable input mechanism 910 (e.g.,506) and/or input mechanism or button (e.g., 508).

In FIG. 9A, device 900 displays a context-specific user interface ondisplay 902. This exemplary context-specific user interface includescurrent time indicator 904 (e.g., a digital clock). Indicator 904 canoptionally include a variety of features or aspects that areindependently editable or configurable by the user. Also included iscomplication 908, which is associated with a calendar application anddisplays a set of information from the calendar application (e.g., dayof the week and the current date).

The user interface screen illustrated in FIG. 9A also includes anon-textual, graphical depiction 906 of a set of information obtainedfrom an application. In this example, depiction 906 depicts a set ofinformation obtained from a weather application: weather conditions(e.g., rain) related to a first temporal context of the current day. Forexample, the temporal context can be the time of a predicted change inweather conditions or time of predicted inclement weather conditions.Non-textual, graphical depictions can include without limitation emojis,symbols, and/or cartoons. In some embodiments, a non-textual, graphicaldepiction is displayed as a wallpaper or background on the userinterface screen.

To view additional graphical depictions of application information, theuser rotates rotatable input mechanism 910 (e.g., with scroll 914 a). Inresponse to detecting scroll 914 a, the device displays scroll indicator912 a, which indicates the position of depiction 906 along a series ofdisplayable graphical depictions.

In response to detecting scroll 914 a, the device displays the screenshown in FIG. 9B. On this screen, the device displays a secondnon-textual, graphical depiction 914 of a set of information obtainedfrom a different application. In this example, depiction 914 depicts aset of information obtained from a navigation application: a reminder toleave for home (e.g., based on estimated driving time from work to home)related to a second temporal context of the current day. For example,the second temporal context can be the time of day associated with theuser's commute home (e.g., a predicted time of day, or a time of dayassociated with one or more previous user inputs indicative of commutinghome). Scroll indicator 912 b is also updated to indicate the positionof depiction 914 along the series of displayable graphical depictions.Text 916 is also displayed and provides a textual description related todepiction 914.

The user can also swipe the touch-sensitive display to scroll the userinterface screen. For example, in response to detecting swipe 914 b,device 900 displays the user interface screen shown in FIG. 9C. Thisscreen includes a third non-textual, graphical depiction 918 of a set ofinformation obtained from a different application. In this example,depiction 918 depicts a set of information obtained from a calendarapplication: a calendar event related to a third temporal context of thecurrent day. For example, the third temporal context can be the time ofthe scheduled calendar event (e.g., a date for coffee). Scroll indicator912 c is also updated to indicate the position of depiction 918 alongthe series of displayable graphical depictions. Text 920 is alsodisplayed and provides a textual description related to depiction 918.

In some embodiments, device 900 can receive data representing textcontent from a depicted set of information and generate the depiction todepict the text content based on the received data. For example, device900 can receive data related to the text content of the calendar event(e.g., “meet Ben for coffee”) and generate depiction 918 using a cartooncoffee cup based on, or in accordance with, the received data. Thisincreases the user interactability of the device, thereby improving theman-machine interface.

In some embodiments, depictions 906, 914, and 918 depict sets ofinformation related to increasingly later temporal contexts of thecurrent day (e.g., moving forward in time). In order to scroll backwardsin time, the user rotates 910 in the opposite direction (e.g., scroll914 c). In response to detecting scroll 914 c, device 900 displays thescreen shown in FIG. 9D. This screen includes depiction 914, and scrollindicator 912 b has been updated to reflect the corresponding positionof depiction 914 along the series.

Any of depictions 906, 914, and 918 can also serve as affordances tolaunch the corresponding application. As shown in FIG. 9E, the user cancontact displayed depiction 906 (e.g., via tap 922). In response todetecting tap 922, device 900 displays a user interface screen from theweather application (FIG. 9F). This allows the user to view additionalinformation from the weather application.

Displayed complications can also serve as affordances to launch thecorresponding application. As shown in FIG. 9G, the user can contactdisplayed complication 908 (e.g., via tap 924). In response to detectingtap 924, device 900 displays a user interface screen from the calendarapplication (FIG. 9H). This allows the user to view additionalinformation from the calendar application, such as the time(s) of one ormore upcoming calendar event(s).

The user may wish to change the application associated with a displayedcomplication (or change the set of information from the applicationdisplayed by the complication). The user presses display 902 with press926 (FIG. 9I). In some embodiments, press 926 is a press having aduration longer than a predetermined duration (e.g., a “long press”input), or a press having a characteristic intensity above apredetermined intensity threshold.

In response to detecting press 926, device 900 visually distinguishesthe user interface screen to indicate edit mode (FIG. 9J). Device 900alerts to the user that it has entered into the selection mode bydisplaying smaller representation 930 of the user interface screen, name932 corresponding to a name of the type of context-specific userinterface currently selected, partial view 934 of an adjacent, storedcontext-specific user interface (which the user could select by swipingto view the full interface and tapping to select it), and editaffordance 936. In order to edit the user interface, the user contactsedit affordance 936 via tap 938.

In response to detecting tap 938, the device enters edit mode andvisually distinguishes one or more aspects of the user interface forediting (FIG. 9K). In this example, complication 908 is selected forediting. Device 900 informs the user that complication 908 is selectedfor editing by visually distinguishing complication 908 via displayingoutline 940 around complication 908 and indicator 942, which indicatesthe application represented by the complication (in this example,indicating the calendar application). Device 900 also displays scrollindicator 944 a, which informs the user that additional applications canbe selected by scrolling and indicates the position of the calendarapplication along the series of displayable application options. Device900 also displays paging affordance 946, which indicates that twooptions for editing different aspects of the user interface can beselected (e.g., by swiping). In this example, the options include theapplication represented by complication 908 and one or more colorsassociated with the user interface (e.g., one or more colors of thecurrent time indicator and/or displayed depictions).

In response to detecting scroll 948 (a rotation of 910), device 900replaces complication 908 with complication 950, which represents astopwatch application (FIG. 9L). In addition, indicator 952 is updatedto indicate the stopwatch application, and scroll indicator 944 b isupdated to reflect the position of the stopwatch application along theseries of displayable application options. In some embodiments, inresponse to detecting one or more additional inputs, device 900 displaysa user interface screen based on the display 902 shown in FIG. 9L (e.g.,a depression of 910 followed by a tap on the displayed user interface inselection mode). In some embodiments, device 900 stores the edited userinterface in memory (e.g., in memory 518 and/or memory 102 of device 100paired or coupled via wireless communication with device 900). In someembodiments, the edited user interface screen can be subsequentlyselected in selection mode, e.g., as described in International PatentApplication Serial No. PCT/US2015/034607, titled “Context-Specific UserInterfaces,” filed Jun. 7, 2015, published as WIPO Publication No.WO/2016/022205 (see, e.g., display 1322 in FIG. 13 ).

FIGS. 10A-10C show a flow diagram illustrating process 1000 forproviding context-specific user interfaces. In some embodiments, process1000 can be performed at an electronic device with a touch-sensitivedisplay, one or more processors, and memory, such as device 100 (FIG.1A), 300 (FIG. 3 ), 500 (FIGS. 5A-5H), or 900 (FIGS. 9A-9L). Someoperations in process 1000 can be combined, the order of some operationsmay be changed, and some operations can be omitted.

In FIG. 10A, at block 1002, the device displays a user interface screencomprising a current time indicator (e.g., 904 in FIG. 9A) and a firstnon-textual, graphical depiction (e.g., 906 in FIG. 9A). As shown atblock 1004, the first non-textual, graphical depiction depicts a firstset of information obtained from a first application, e.g., a calendarevent, user photo, change in weather conditions, breathe or activityreminder, and so forth (additional sets of information are describedsupra). As shown at block 1006, the first set of information relates toa first temporal context of the current day. For example, depiction 906depicts forecasted weather conditions obtained from a weatherapplication related to an upcoming time of the current day.

At block 1008, the device detects a user input. In some embodiments, theuser input comprises a rotation of a rotatable input mechanism (e.g.,scroll 914 a received at rotatable input mechanism 910 shown in FIG.9A). In some embodiments, the first user input comprises a swipe on atouch-sensitive display (e.g., swipe 914 b on display 902 shown in FIG.9B).

At block 1010, in response to detecting the user input, the deviceceases to display the first non-textual, graphical depiction.

At block 1012, in response to detecting the user input, the devicedisplays a second non-textual, graphical depiction (see depiction 914 inFIG. 9B). As shown at block 1014, the second non-textual, graphicaldepiction depicts a second set of information obtained from a secondapplication. As shown at block 1016, the second set of informationrelates to a second temporal context of the current day. For example,depiction 914 depicts forecasted traffic conditions obtained from anavigation application related to the user's upcoming commute home. Insome embodiments, the first and the second applications are the same. Insome embodiments, the first and the second applications are different.In some embodiments, the first and the second non-textual, graphicaldepictions are displayed as wallpapers or backgrounds on the userinterface screen. In some embodiments, the first and/or second set(s) ofinformation are selected by the device for display based on one or moreselection criteria, as described supra. Displaying sets of informationobtained from different applications, but relating to time(s) in thecurrent day, provides the user with relevant application data (andoptionally affordances for launching applications) from a variety ofapplications without necessitating the display of multiple, dedicatedapplication widgets (each dedicated to, and showing information obtainedfrom, a single application). Providing additional control optionswithout cluttering the user interface with additional displayed controls(e.g., dedicated application widgets) enhances the operability of thedevice and makes the user-device interface more efficient (e.g., byhelping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In FIG. 10B, at block 1018, the device optionally receives datarepresenting text content from the second set of information in responseto detecting the user input (e.g., before displaying the secondnon-textual, graphical depiction). For example, text content cancomprise one or more keywords.

At block 1020, in response to detecting the user input, the deviceoptionally generates the second non-textual, graphical depiction todepict the text content based on the received data (e.g., a cup ofcoffee to depict a “coffee” keyword, as shown by depiction 918 in FIG.9C). Thus, the device automatically generates a graphical depiction oftext content related to application data (e.g., a calendar event) andsurfaces the depiction to the user at a relevant time of day (e.g.,based on one or more selection criteria, as described supra) withoutrequiring the user to select the application data (e.g., select akeyword from a calendar event) or when to display it. Performing anoperation when a set of conditions has been met without requiringfurther user input enhances the operability of the device and makes theuser-device interface more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

At block 1022, in response to detecting the user input, the deviceoptionally displays an indicator of position along a series of positions(e.g., scroll indicators 912 a-912 c in FIGS. 9A-9D). The indicator ofposition along a series of positions indicates a position of the secondnon-textual, graphical depiction along a series of displayablenon-textual, graphical depictions. Displaying an updating scrollindicator that indicates a position of a currently displayed depictionalong a series of displayable depictions provides feedback to the userthat the received user input (e.g., scroll 914 a in FIG. 9A, scroll 914c in FIG. 9C, or swipe 914 b in FIG. 9B) controls display of depictionsthat include application information while helping the user to navigatethrough the entire series of depictions (as well as indicating to theuser that additional depictions are displayable). Providing improvedfeedback enhances the operability of the device and makes theuser-device interface more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

At block 1024, detecting the user input comprises detecting a swipe(e.g., on a touch-sensitive display) in a first swipe direction. Seeswipe 914 b on display 902 shown in FIG. 9B.

At block 1026, the device optionally detects a second swipe in a seconddirection different from the first swipe direction.

At block 1028, in response to detecting the second swipe, the deviceoptionally ceases to display the second non-textual, graphicaldepiction.

At block 1030, in response to detecting the second swipe, the deviceoptionally displays the first non-textual, graphical depiction on thedisplay.

At block 1032, detecting the user input comprises detecting a rotationof a rotatable input mechanism in a first direction of rotation (e.g.,scroll 914 a received at rotatable input mechanism 910 shown in FIG.9A).

At block 1034, the device optionally detects a second rotation in asecond direction different from the first direction of rotation.

At block 1036, in response to detecting the second rotation, the deviceoptionally ceases to display the second non-textual, graphicaldepiction.

At block 1038, in response to detecting the second rotation, the deviceoptionally displays the first non-textual, graphical depiction on thedisplay.

In FIG. 10C, at block 1040, the device optionally displays an affordancerepresenting a calendar application (e.g., complication 908 in FIG. 9G).In some embodiments, as shown at block 1042, the affordance indicatesthe current date.

At block 1044, the device optionally detects a user input correspondingto a selection of the affordance (e.g., tap 924 on complication 908 inFIG. 9G).

At block 1046, in response to detecting the user input corresponding toa selection of the affordance, the device launches the calendarapplication (see FIG. 9H). In some embodiments, launching the calendarapplication comprises ceasing to display the user interface screen anddisplaying a second user interface screen corresponding to the calendarapplication.

Note that details of the processes described above with respect toprocess 1000 (e.g., FIGS. 10A-10C) are also applicable in an analogousmanner to the methods described elsewhere in this application. Forexample, other methods described in this application may include one ormore of the characteristics of process 1000. For example, one or more ofthe steps of process 1000 can be combined with one or more of the stepsof processes 700 or 800, as described above. For brevity, these detailsare not repeated below.

Turning now to FIG. 11A, users may wish to generate new images fordisplay on a portable multifunction device, e.g., to provide the userdifferent experiences as the display is viewed multiple times a day.This keeps the user interested and engaged with the electronic device.Tying the generation of these new images to the time of day providesimproved techniques for timekeeping and further enhances the timekeepingfunctionality of the device.

FIGS. 11A-11N show exemplary context-specific user interfaces that maybe operated on device 1100. Device 1100 may be device 100, 300, or 500in some embodiments. The electronic device has a display 1102 (e.g.,504). In some embodiments, display 1102 is a touch-sensitive display. Insome embodiments, device 1100 includes a rotatable input mechanism 1120a (e.g., 506) and/or input mechanism or button 1120 b (e.g., 508).

FIG. 11A (top) illustrates an exemplary context-specific user interfacedisplayed on display 1102 of device 1100. This user interface screenincludes current time indicator 1104 (in this example, an analog clockwith an hour hand, minute hand, and optional seconds hand). Alsodisplayed in association with 1104 are three complications 1106, 1108,and 1110. These three complications are each associated with anapplication (an alarm, weather, and calendar application, respectively).In some embodiments, one or more of these complications displays a setof information obtained from the corresponding application. For example,complication 1108 displays a current temperature obtained from theweather application, and complication 1110 displays the time of anupcoming calendar event and a text descriptor. In some embodiments,complication 1110 occupies more space on display 1102 and optionallydisplays more information from the corresponding application (e.g., anincreased number of characters or increased image size), as compared tocomplications 1106 and 1108. This provides the user with multiple levelsof detail for displaying application information. Complication 1106graphically represents the alarm application without displaying a set ofinformation from the alarm application (textual representations couldalso be used).

Also displayed on this user interface screen is background 1112 a. Insome embodiments, background 1112 a is displayed as a wallpaper ondisplay 1102. In some embodiments, background 1112 a is displayed as theclock face of analog clock 1104.

Background 1112 a displays a kaleidoscope-style composite image 1118(FIG. 11A, bottom) created from image 1114 (FIG. 11A, middle). Device1100 creates composite image 1118 by selecting portion 1116 of image1114 and reflecting portion 1116 across a plurality of axes ofreflection. For example, device 1100 can display 12 facets of portion1116 mirrored 6 times, or any other combination of number of axes ofreflection and number of facets to generate a suitable image.

FIG. 11A shows composite image 1118 displayed as background 1112 a ondisplay 1102 at 10:09. Later, when the user activates the display (e.g.,as described infra) at 12:25, multiple aspects of display 1102 areupdated (FIG. 11B). Current time indicator 1104 is updated to reflectthe current time. In some embodiments, the set(s) of informationdisplayed by one or more complication(s) are updated, e.g., inaccordance with data from the corresponding application. In thisexample, complication 1108 is updated to display the currenttemperature, and complication 1110 is updated to display the time of anupcoming calendar event and a text descriptor. Complication 1106 is notupdated.

Background 1112 b is also updated. Device 1100 creates composite image1124 by selection portion 1122 of image 1114 and reflecting portion 1122across a plurality of axes of reflection (in some embodiments, the sameaxes of reflection used to generate composite image 1118). Thus, device1100 can select different portions of the same image at different timesof day, thereby increasing the variety of its displayed background.

In some embodiments, the selection of the image portion is based on timeof day. This concept is illustrated in FIG. 11C. Like FIG. 11A, display1102 in FIG. 11C (top) shows a user interface screen with current timeindicator 1104 and complications 1106, 1108, and 1110. Analog clock 1104indicates that the current time is the same time as shown in FIG. 11A,e.g., on a different day. Complication 1108 has been updated to indicatethe current temperature, and complication 1110 has been updated toindicate the time of an upcoming calendar event and a text descriptor.Complication 1106 is not updated.

Background 1112 c in FIG. 11C is the same as background 1112 a in FIG.11A. For example, background 1112 c is created by device 1100 byselecting portion 1116 of image 1114 and reflecting portion 1116 acrossthe same plurality of axes of reflection. Thus, the selection and/orreflection of an image portion can be determined based on time of day.

In some embodiments, device 1100 can select a portion (e.g., portion1116) of an image (e.g., image 1114) based on a set of one or morecriteria. In some embodiments, device 1100 can associate a score (e.g.,an “interestingness score”) with a plurality of portions of an image(e.g., 1114). For example, device 1100 can divide an image into aplurality of portions (e.g., a grid) and associate a score with eachportion of the plurality. In some embodiments, the score is based on oneor more of the following scoring criteria: luminance, average luminance,derivative of luminance, and chroma value. In some embodiments, device1100 selects a portion based on its score (e.g., it selects a portionhaving a score above a predetermined threshold). This is advantageous,e.g., because some image portions may be incompatible with reflection(e.g., an image portion having a single color or black/white hue wouldnot be amendable to reflection and composite image generation).

In some embodiments, device 1100 can apply a selection path through theimage to select image portions based on time of day. For example, theselection path can be a deterministic path guiding portion selectionthat repeats at a regular interval, such as every 12 or every 24 hours.Thus, a user can perceive the time of day based on which portion of theimage is selected and displayed as a kaleidoscope. In some embodiments,the selection path comprises two or more image portions having aselection score above a predetermined threshold (e.g., as describedabove). In some embodiments, device 1100 detects a user input (e.g., arotation of a rotatable input mechanism), and in response to detectingthe user input, the device selects a second image portion along theselection path for reflection and composite image generation. In someembodiments, the user can select an image portion, e.g., by providing auser input corresponding to a selection of an image portion.

Device 1100 can apply a variety of axes of reflection to an imageportion, thereby generating kaleidoscope-type composite images in avariety of patterns. Exemplary patterns based on portion 1116 of image1114 are shown in FIG. 11D. In some embodiments, the axes of reflectioncreate a kaleidoscope pattern, e.g., by applying multiple axes ofreflection to create a set of reflected facets. In some embodiments, theaxes of reflection create a radial pattern, e.g., by taking a slice ofthe image and rotating the slice in a circle to create a plurality ofaxes of reflection. In some embodiments, the axes of reflection create atessellated pattern, e.g., by tiling the background with a series ofreflected image portions. Various types of tessellations are known andare well known in the work of the artist M. C. Escher; see, e.g.,repeated triangles to generate a sphere (e.g., a Schwarz triangle), ortiling in a hyperbolic plane (e.g., a Poincaré disk). In someembodiments, the axes of reflection create a pattern based on theFibonacci sequence, e.g., by repeating reflected image portions innumbers of spirals according to the Fibonacci sequence (such as thenumber of seed spirals on a sunflower).

This context-specific user interface allows the user to launch anapplication by selecting the corresponding complication. For example,the user contacts complication 1108 (e.g., via tap 1120) in FIG. 11E. Inresponse to detecting tap 1120, device 1100 updates display 1102 to showa user interface from the corresponding weather application (FIG. 11F).

The user may wish to view the original image, e.g., to identify theportion selected for composite image generation. The user contactsbackground 1112 a (e.g., via tap 1122) in FIG. 11G. In response todetecting tap 1122, the device displays image 1114, e.g., as background1124.

The user may wish to edit the application represented by complication1108 and/or other aspects of the user interface, such as colors (e.g., acolor of a seconds hand of 1104), density of displayed information(e.g., hour markings of 1104, or lack thereof), and so forth. Additionaldescriptions of editing and/or selecting context-specific userinterfaces and sub-components thereof may be found in InternationalPatent Application Serial No. PCT/US2015/034607, titled“Context-Specific User Interfaces,” filed Jun. 7, 2015, published asWIPO Publication No. WO/2016/022205, which is incorporated by referenceherein in its entirety.

In FIG. 11I, the user accesses an edit mode of device 1100 through press1130, which in some embodiments can be a press having a duration longerthan a predetermined duration (e.g., a “long press” input) or a contacthaving a characteristic intensity above an intensity threshold. In thisexample, in response to detecting press 1130, device 1100 enters acontext-specific user interface selection mode and visuallydistinguishes the user interface screen to indicate the selection mode(FIG. 11J). Device 1100 alerts to the user that it has entered into theselection mode by displaying smaller representation 1132 of the userinterface screen, name 1136 corresponding to a name of the type ofcontext-specific user interface currently selected, partial view 1138 ofan adjacent, stored context-specific user interface (which the usercould select by swiping to view the full interface and tapping to selectit), and edit affordance 1134. In order to edit the user interface, theuser contacts edit affordance 1134 via tap 1140.

In response to detecting tap 1140, the device enters edit mode andvisually distinguishes one or more aspects of the user interface forediting (FIG. 11K). In this example, background 1140 is selected forediting (e.g., selecting a photo from which the portion is selected).Device 1100 informs the user that background 1140 is selected forediting by visually distinguishing background 1140 via displaying anoutline around background 1140 and indicator 1142, which indicates thatthe source photo for background 1140 is editable. Device 1100 alsodisplays scroll indicator 1146, which informs the user that additionalphotos can be selected by scrolling and indicates the position of thephoto along the series of displayable photo-based backgrounds. Device1100 also displays paging affordance 1144, which indicates that threeoptions for editing different aspects of the user interface can beselected (e.g., by swiping). In this example, the options include thephoto from which background 1140 is selected, the application associatedwith various complications, and the type of pattern used to generate thecomposite image.

To edit the photo, the user can rotate 1120 a. To edit a differentaspect of the interface, the user swipes display 1102 via swipe 1148. Inresponse to detecting swipe 1148, the device indicates complication 1108for editing (FIG. 11L). Device 1100 informs the user that complication1108 is selected for editing by visually distinguishing complication1108 via displaying outline 1150 around complication 1108 and indicator1152, which indicates the application represented by the complication(in this example, indicating the weather application). Device 1100 alsodisplays scroll indicator 1154, which informs the user that additionalapplications can be selected by scrolling and indicates the position ofthe weather application along the series of displayable applicationoptions. Further in response to detecting swipe 1148, device 1100updates paging affordance 1144 to reflect the position of complicationediting in the series of editable aspects.

To select the pattern used to generate the composite image, the userswipes display 1102 via swipe 1156. In response to detecting swipe 1156,the device displays the screen shown in FIG. 11M. In FIG. 11M, thecomposite image 1158 on which the background is based is visuallyindicated via displaying outline 1158 a around composite image 1158 andindicator 1158 b, which indicates that the pattern (e.g., of axes ofreflection) used to generate the composite image 1158 for background1140 is editable. Device 1100 also displays scroll indicator 1160 a,which informs the user that patterns can be selected by scrolling andindicates the position of the pattern along the series of selectablepatterns. Further in response to detecting swipe 1156, device 1100updates paging affordance 1144 to reflect the position of patternediting in the series of editable aspects.

To change the pattern, the user rotates 1120 a via scroll 1162. Inresponse to detecting scroll 1162, device 1100 generates composite image1166 using the same image portion as 1158, but applying a differentpattern of axes of reflection (FIG. 11N). Indicator 1158 b is alsoupdated to reflect the pattern of axes of reflection. Scroll indicator1160 b is also updated to indicate the position of the radial patternalong the series of selectable pattern options. In some embodiments, theuser can then exit edit mode and display the edited user interfacescreen. In some embodiments, upon exiting edit mode, the device savesthe edited user interface screen in memory, e.g., such that it can besubsequently selected in selection mode, e.g., as described inInternational Patent Application Serial No. PCT/US2015/034607, titled“Context-Specific User Interfaces,” filed Jun. 7, 2015, published asWIPO Publication No. WO/2016/022205 (see, e.g., display 1322 in FIG. 13).

Turning now to FIG. 12 , it may be advantageous to allow the user to usean electronic device (e.g., a first device) to configure acontext-specific user interface for a different portable multifunctiondevice (e.g., a second device). In some embodiments, the first devicehas a larger display than the second device, thereby making it easierfor the user to see and/or provide touch gestures on the first device.The user may wish to configure a user interface for the second devicewhile operating the first device without switching over to the seconddevice.

FIG. 12 illustrates an exemplary first electronic device 1200 and anexemplary second electronic device 1210. In some embodiments, device1200 may be one or more of devices 100 (FIG. 1A), 300 (FIG. 3 ), and/or500 (FIG. 5A). For purposes of illustration, first device 1200 is apersonal electronic device, similar to portable multifunction device 100as depicted in FIG. 4A, with a touch-sensitive display 1202. In someembodiments, second device 1210 may be one or more of devices 100 (FIG.1A), 300 (FIG. 3 ), and/or 500 (FIG. 5A). For purposes of illustration,external device 1210 is a personal electronic device, similar to device500 as depicted in FIG. 5A, with a touch-sensitive display 1212, arotatable input mechanism, and a button.

As depicted in FIG. 12 , device 1200 is capable of receiving informationover a wireless network. In some embodiments, device 1200 is coupled viawireless communication to device 1210. FIG. 12 also indicates thatdevice 1200 is capable of operating in a paired relationship withexternal device 1210 to exchange data between the two devices. In apaired relationship, device 1200 and device 1210 are registered with oneanother and can perform two-way wireless communication. In someembodiments, wireless communication, for purposes of a pairedrelationship, occurs over a peer-to-peer wireless communication protocolsuch as Bluetooth and/or Bluetooth Low Energy (BTLE). In someembodiments, the wireless communication uses more than one wirelesscommunication protocol. For example, WiFi may be used in addition toBTLE. In these embodiments, an initial communication between two devicesmay occur over a lower powered protocol, such as BTLE, even if theprotocol yields a slower data transfer speed. Subsequent communicationsmay occur over a secondary network that is relatively faster, such asWiFi. Additional exemplary techniques related to initiating andoperating in a paired relationship are described in the followingco-pending applications: International Patent Application Serial No.PCT/US2015/023699, titled “Companion Application for ActivityCooperation,” filed Mar. 31, 2015 published as WIPO Publication No.WO/2015/0183403; U.S. patent application Ser. No. 14/474,466, titled“Predefined Wireless Pairing,” filed Sep. 2, 2014, published as US PGPub. No. 20150350865; International Patent Application Serial No.PCT/US2015/047507, titled “Reduced-size Configuration Interface,” filedAug. 28, 2015 published as WIPO Publication No. WO/2016/036603; and U.S.Provisional Patent Application titled “Reduced-size ConfigurationInterface,” filed Mar. 8, 2015, naming Lawrence Y. Yang et al. asinventors. Referring to FIG. 12 , a user may wish to configure a contextspecific user interface using device for display on device 1210 usingdevice 1200.

FIG. 13 illustrates exemplary electronic device 1300 and an exemplaryelectronic device 1320. In some embodiments, device 1300 may be one ormore of devices 100 (FIG. 1A), 300 (FIG. 3 ), and/or 500 (FIG. 5A). Forpurposes of illustration, first device 1300 is a personal electronicdevice, similar to portable multifunction device 100 as depicted in FIG.4A, with a touch-sensitive display 1302. In some embodiments, seconddevice 1320 may be one or more of devices 100 (FIG. 1A), 300 (FIG. 3 ),and/or 500 (FIG. 5A). For purposes of illustration, external device 1320is a personal electronic device, similar to device 500 as depicted inFIG. 5A, with a touch-sensitive display 1322 and a rotatable inputmechanism 1324. Devices 1300 and 1320 are coupled via wirelesscommunication. In some embodiments, devices 1300 and 1320 are in apaired relationship, e.g., as described in reference to FIG. 12 .

Device 1320 has access to a library of context-specific user interfacesfor display on display 1322. For example, the library can be stored inmemory of device 1320, stored in memory of device 1300 and accessible todevice 1320, and/or stored at an external server accessible to devices1300 and 1320. In some embodiments, context-specific user interfaces arestored in the library as unique or complete assets. In some embodiments,the library stores context-specific user interfaces as configurationsthat are rendered for display by device 1320 (e.g., by rendering a setof graphical assets stored in memory according to the configuration,which specifies the particular graphical asset(s) used and theirarrangement within the user interface).

FIG. 13 also illustrates a user interface, at device 1300, forselecting, reordering, and/or editing context-specific user interfacesfrom the stored library for display on device 1320. The user interfacescreen shown on display 1302 includes depiction 1304 of device 1320,which optionally includes a depiction of device name, size, and/or otherdevice features. In some embodiments, depiction 1304 serves as anaffordance that, when contacted by the user, displays additionalinformation and/or functionality related to device 1320, such as optionsfor pairing or de-pairing device 1320 with another electronic device.The user interface screen shown on display 1302 includes complicationsbar 1306. In some embodiments, complications bar 1306 allows the user toview a list of complications that can be configured for display as partof a context-specific user interface from the library, as well asoptional affordances for selecting and/or editing particularcomplications. In some embodiments, the user scrolls on the depicteduser interface screen (e.g., with a horizontal swipe) to view particularcomplication options. Screen 1302 further includes affordance 1308 forviewing one or more user interfaces from the library. In someembodiments, the user touches affordance 1308, and in response device1300 displays the user interface illustrated on screen 1302.

Also shown on the user interface screen of display 1302 are previewimages 1310, 1312, and 1314. Preview images 1310, 1312, and 1314represent context-specific user interfaces from the library for displayon device 1320. As represented by preview images 1310 and 1312, bothcorresponding user interfaces include a clock. In addition, the userinterface represented by 1312 includes a complication, as describedherein. In some embodiments, the preview image(s) are displayed with anassociated text element indicating the type of watch face for thecorresponding context-specific user interface (e.g., “sun” for the userinterface represented by 1310, “utility” for the user interfacerepresented by 1312, etc.). The user interface screens shown on displays1302 and 1322 indicate to the user what user interfaces are stored inthe library and the order or sequence of the user interfaces within thelibrary.

In some embodiments, the preview image includes a representation of oneor more complications of the user interface. For example, preview image1312 includes representation 1316, which represents a complication ofthe user interface represented by 1312. In this example, representation1316 represents a complication that displays an affordance representinga weather application. As discussed above, complications can obtain dataand display information obtained from an associated application(optionally, the information is updated in accordance with updates tothe data). In some embodiments, device 1300 obtains “live” data from theweather application and displays information updated according toupdates to the data in representation 1316 (e.g., the sun depicted in1316 indicates current weather conditions, representing live dataobtained from the weather application). Advantageously, this allows theuser to visualize how the user interface looks when displayed on device1320 at the current time. In other embodiments, device 1300 displays a“placeholder” representation of application data. For example, the sundepicted in 1316 can be an icon or affordance that represents to theuser the content of the live data that would be displayed in thecomplication. For example, the placeholder may be installed as part ofthe app and/or designated as part of a software development kit used todevelop the application. Advantageously, this allows the user tounderstand the function of the complication within the user interfacebut does not require processor resources and/or communication bandwidthto obtain live data to generate the preview image.

Preview image 1314 is shown in partial view. This alerts the user to thefact that additional preview images representing the rest of the storedlibrary are viewable in this interface, e.g., by scrolling. In someembodiments, the user swipes the display at one or more of previewimages 1310, 1312, and 1314 (e.g., a horizontal swipe), and in responseto detecting the swipe, device 1300 scrolls the displayed preview imagesto reveal one or more additional preview images representing userinterfaces from the library.

In some embodiments, information in one or more preview images shown ondisplay 1302 and/or 1322 is updated live, e.g., while the user is inface selection mode of device 1320 or viewing preview images at display1302. For example, in some embodiments, a representation of a clock onone or more of 1310, 1312, 1314, 1330, 1332, and/or 1334 is renderedlive, e.g., such that the preview image displays current time. In someembodiments, a representation of one or more complications on one ormore of 1310, 1312, 1314, 1330, 1332, and/or 1334 is rendered live,e.g., such that the preview image displays current complication data(e.g., information from an application updated in accordance withupdates to application data). In some embodiments, a representation ofone or more complications on a currently centered preview image (e.g.,displayed in complete view, such as 1310 or 1330) is rendered live,while a representation of one or more complications on a currentlynon-centered preview image (e.g., displayed in partial view, such as1312, 1314, 1332 or 1334) is not rendered live (e.g., it displaysplaceholder data, or data obtained at a previous refresh, such as thelast time the represented user interface was displayed, or the last timethe preview image was centered on the display). In some embodiments, arepresentation of one or more complications on a currently centeredpreview image (e.g., displayed in complete view, such as 1310 or 1330)and representation(s) on preview images immediately adjacent to thecurrently centered preview image are rendered live (e.g., 1312, 1314,1332 or 1334), while a representation of one or more complications on apreview image that is not currently centered and not adjacent to acurrently centered preview image is not rendered live (e.g., it displaysplaceholder data, or data obtained at a previous refresh, such as thelast time the represented user interface was displayed, or the last timethe preview image was centered on the display). In some embodiments, arepresentation that is not rendered live may be rendered using dataupdated at a longer interval than a representation that is renderedlive. In some embodiments, one or more elements or user interfaceobjects represented in a preview image other than those representing aclock or a complication may be shown as a static element (e.g., notrendered according to updated data).

FIG. 14A illustrates exemplary electronic device 1400. In someembodiments, device 1400 may be one or more of devices 100 (FIG. 1A),300 (FIG. 3 ), and/or 500 (FIG. 5A). For purposes of illustration,device 1400 is a personal electronic device, similar to portablemultifunction device 100 as depicted in FIG. 4A, with a touch-sensitivedisplay 1402. In some embodiments, device 1400 is in a pairedrelationship (e.g., as described in reference to FIG. 12 ) with a seconddevice (e.g., 1210 or 1320), which may be one or more of devices 100(FIG. 1A), 300 (FIG. 3 ), and/or 500 (FIG. 5A).

Display 1402 includes preview image 1404 of a context-specific userinterface, similar to those described in FIGS. 11A-11N, for display onthe second device. Also displayed are a number of editable aspects ofthe context-specific user interface. In this example, the user can editthe image used to create a composite image for the background, theapplications and/or sets of information displayed by one or morecomplications, and the type of pattern (e.g., of axes of reflection)used to generate the composite image. Representations of selectableoptions for these editable aspects are also displayed. For example,representations 1406, 1408, and 1410 represent images that can beselected for composite image generation. In some embodiments, one ormore of the images are system-designated or curated images. In someembodiments, one or more of the images are user-designated images, e.g.,photos taken by the user. Representations 1412, 1414, and 1416 representtypes of pattern (e.g., of axes of reflection) that can be used togenerate a composite image-based background (e.g., as described supra).

FIGS. 14B & 14C illustrate selection of an option for pattern. Akaleidoscope pattern is currently selected for generation of a compositeimage displayed as background 1462 a on display 1452 of device 1450 inFIG. 14B. Display 1452 also shows complications 1456, 1458, and 1460,and current time indicator 1454. The screen on display 1402 of device1400 also informs the user of this currently selected option usingrepresentation 1404, which represents the user interface currentlyselected for display by device 1450.

In FIG. 14B, the user selects representation 1414, which represents aradial pattern (e.g., of axes of reflection). In this example, the usercontacts representation 1414 displayed on display 1402 of device 1400via tap 1420. In some embodiments, representation 1414 further comprisesrepresentations of one or more of complications 1456, 1458, and 1460,and current time indicator 1454.

In response to detecting tap 1420, device 1400 updates representation1404 with a representation of a composite image generated using a radialpattern of reflection (FIG. 14C). In some embodiments, representation1404 represents the same interface displayed by 1450. In someembodiments, representation 1404 represents an interface comprising aplaceholder composite-image based background that represents the radialpattern to the user. This informs the user at device 1400 how theselected option will change the user interface screen displayed bydevice 1450. In some embodiments, representation 1404 further comprisesrepresentations of one or more of complications 1456, 1458, and 1460(e.g., using live application data or placeholder data), and currenttime indicator 1454.

Further in response to detecting tap 1420 at device 1400, device 1450updates background 1462 b to generate a composite image using the radialpattern (e.g., of axes of reflection; FIG. 14C). Compared to background1462 a, background 1462 b is based on the same image portion, butreflected across a different plurality of axes of reflection (e.g., in aradial pattern). For example, device 1400 can send instructions todevice 1450 to generate a composite image using the radial pattern inresponse to detecting tap 1420.

FIGS. 14D & 14E illustrate selection of an image for the background. Aphoto of a bridge is currently selected for generation of a compositeimage displayed as background 1462 a on display 1452 of device 1450 inFIG. 14D. Display 1452 also shows complications 1456, 1458, and 1460,and current time indicator 1454. The screen on display 1402 of device1400 also informs the user of this currently selected option usingrepresentation 1404, which represents the user interface currentlyselected for display by device 1450.

In FIG. 14D, the user selects representation 1408, which represents adifferent image of a beach. In this example, the user contactsrepresentation 1408 displayed on display 1402 of device 1400 via tap1430.

In response to detecting tap 1420, device 1400 updates representation1404 with a representation of a composite image generated using a radialpattern of reflection (FIG. 14E). In some embodiments, representation1404 represents the same interface displayed by 1450. In someembodiments, representation 1404 represents an interface comprising aplaceholder composite-image based background that represents the radialpattern to the user. This informs the user at device 1400 how theselected option will change the user interface screen displayed bydevice 1450. In some embodiments, representation 1404 further comprisesrepresentations of one or more of complications 1456, 1458, and 1460(e.g., using live application data or placeholder data), and currenttime indicator 1454.

Further in response to detecting tap 1430 at device 1400, device 1450updates background 1462 c to generate a composite image using the beachphoto (FIG. 14E). Compared to background 1462 a, background 1462 c usesthe same plurality of axes of reflection (e.g., in a kaleidoscopepattern), but applied to a different image portion (e.g., a portion ofthe beach photo instead of the bridge photo. For example, device 1400can send instructions to device 1450 to generate a composite image usingthe beach photo in response to detecting tap 1430.

FIGS. 15A-15E show a flow diagram illustrating process 1500 forproviding context-specific user interfaces. In some embodiments, stepsof process 1500 can be performed at an electronic device with atouch-sensitive display, one or more processors, and memory, such asdevice 100 (FIG. 1A), 300 (FIG. 3 ), 500 (FIGS. 5A-5H), 1100 (FIGS.11A-11N), 1400 (FIGS. 14A-14E), or 1450 (FIGS. 14A-14E). Some operationsin process 1500 can be combined, the order of some operations may bechanged, and some operations can be omitted.

In FIG. 15A, at block 1502, the device displays a user interface screencomprising a current time indicator (e.g., indicator 1104 in FIG. 11A)and a background. In some embodiments, the current time indicatorcomprises an analog or digital clock.

At block 1504, the device detects a change in time.

At block 1506, in response to detecting the change in time, the deviceselects a first portion of an image (e.g., portion 1116 of image 1114 inFIG. 11A). In some embodiments, the first portion is less than theentire image. In some embodiments, the image is a system-designated orcurated image. In some embodiments, the image is a user-designatedimage, such as a user photo (e.g., stored on the device, or on a devicein wireless communication with the device). In some embodiments, thedevice automatically selects the first portion of the image (e.g., inthe absence of a user input corresponding to a selection of the imageportion). Automatically selecting the portion of the image using thedevice enhances the variety of backgrounds that can be displayed by thedevice without requiring the user to select a portion each time theimage changes (e.g., numerous backgrounds can be displayed during agiven day without the user having to select each time the backgroundchanges). Performing an operation when a set of conditions has been metwithout requiring further user input enhances the operability of thedevice and makes the user-device interface more efficient (e.g., byhelping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

At block 1508, in response to detecting the change in time, the devicereflects the first portion across a first plurality of axes ofreflection to generate a first plurality of reflected portions. In someembodiments, the first plurality of axes of reflection is based on apattern selected from kaleidoscope, radial reflection, Fibonaccisequence, and tessellation (see FIG. 11D).

At block 1510, in response to detecting the change in time, the devicereplaces the background with a first composite image comprising thefirst plurality of reflected portions (e.g., background 1118 in FIG.11A).

At block 1512, the device detects a second change in time.

At block 1514, in response to detecting the second change in time, thedevice selects a second portion of the image (e.g., portion 1122 ofimage 1114 in FIG. 11B). In some embodiments, the second portion is lessthan the entire image. In some embodiments, the second portion isdifferent from the first portion. In some embodiments, the image is asystem-designated or curated image. In some embodiments, the image is auser-designated image, such as a user photo (e.g., stored on the device,or on a device in wireless communication with the device). In someembodiments, the device automatically selects the second portion of theimage (e.g., in the absence of a user input corresponding to a selectionof the image portion). Automatically selecting the portion of the imageusing the device enhances the variety of backgrounds that can bedisplayed by the device without requiring the user to select a portioneach time the image changes (e.g., numerous backgrounds can be displayedduring a given day without the user having to select each time thebackground changes). Performing an operation when a set of conditionshas been met without requiring further user input enhances theoperability of the device and makes the user-device interface moreefficient (e.g., by helping the user to provide proper inputs andreducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

At block 1516, in response to detecting the second change in time, thedevice reflects the second portion across a second plurality of axes ofreflection to generate a second plurality of reflected portions. In someembodiments, the first plurality and the second plurality of axes ofreflection are the same. In some embodiments, the second plurality ofaxes of reflection is based on a pattern selected from kaleidoscope,radial reflection, Fibonacci sequence, and tessellation (see FIG. 11D).

At block 1518, in response to detecting the second change in time, thedevice replaces the background with a second composite image comprisingthe second plurality of reflected portions (e.g., background 1124 inFIG. 11B).

In FIG. 15B, at block 1520, the device optionally creates a data fileencoding the second composite image. This allows the device to createand store new data files encoding images without requiring multiple userinputs, e.g., to select an image, select axes of reflection, andreflecting the image portions. Performing an operation when a set ofconditions has been met without requiring further user input enhancesthe operability of the device and makes the user-device interface moreefficient (e.g., by helping the user to provide proper inputs andreducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

At block 1522, the device optionally stores the data file in memory. Insome embodiments, the data file is stored in memory of the device (e.g.,device 1320 in FIG. 13 ). In some embodiments, the data file is storedin memory of a device in wireless communication with the device (e.g.,device 1300 in FIG. 13 ).

At block 1524, the device optionally selects the first portion of theimage based on time of day when the first change of time is detected,and the device optionally selects the second portion of the image basedon time of day when the second change of time is detected. In someembodiments, as shown in block 1526, the device applies a selection paththrough the image (e.g., a deterministic path that selects imageportions based on time of day) to select the second portion of the imagebased on time of day when the second change in time is detected. In someembodiments, as shown in block 1528, the selection path comprises apredetermined path of portions through an image that repeats at aregular interval (e.g., 12 or 24 hours). Thus, the device displays animage-based background that indicates the time of day (e.g., since thesame portion is selected at the same time of day, or since the sameportion is selected twice a day such as at 10:00 am and 10:00 pm),thereby providing additional feedback to the user indicative of the timeof day. Providing improved feedback enhances the operability of thedevice and makes the user-device interface more efficient (e.g., byhelping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

At block 1530, the device optionally detects a third change in time. Insome embodiments, the third change in time is detected at the same timeof day as the second change in time but on a different day.

At block 1532, the device optionally displays the second composite imagein response to detecting the third change in time (e.g., background 1118in FIG. 11C).

At block 1534, in response to detecting the second change in time, thedevice optionally updates the current time indicator to reflect currenttime when the second change in time is detected (e.g., indicator 1112 bin FIG. 11B).

In some embodiments, the device is coupled via wireless communication toa second electronic device with a display, one or more processors, andmemory. In some embodiments, the second electronic device is a personalelectronic device, similar to portable multifunction device 100 asdepicted in FIG. 4A, with a touch-sensitive display 1402. In someembodiments, the second electronic device is in a paired relationship(e.g., as described in reference to FIG. 12 ) with the device, which maybe one or more of devices 100 (FIG. 1A), 300 (FIG. 3 ), and/or 500 (FIG.5A).

In FIG. 15C, at block 1536, the second electronic device optionallydisplays a second user interface screen with a first preview image thatrepresents the first image and a second preview image that represents asecond image (see, e.g., representations 1406 and 1408 on display 1402in FIG. 14D). In some embodiments, this occurs after the first devicereplaces the first composite image with the second composite image.

At block 1538, the second electronic device optionally detects a userinput corresponding to a selection of the second preview image. In someembodiments, detecting the user input corresponding to the selection ofthe second preview image comprises detecting a contact on thetouch-sensitive display of the second electronic device at (e.g., on ornear) the displayed second preview image (e.g., tap 1430 in FIG. 14D).In some embodiments, the second image is a user photo stored in thememory of the second electronic device. In some embodiments, detectingthe user input corresponding to a selection of the second preview imagecomprises displaying a third user interface screen comprising aplurality of preview images (e.g., a user interface screen of imagemanagement module 144). In some embodiments, the plurality of previewimages represents a plurality of user photos. In some embodiments, theplurality of preview images comprises the second preview image.

At block 1540, in response to detecting the user input corresponding toa selection of the second preview image, the first or second electronicdevice optionally selects a portion of the second image.

At block 1542, in response to detecting the user input corresponding toa selection of the second preview image, the first or second electronicdevice optionally reflects the portion of the second image across aplurality of axes of reflection to generate a third plurality ofreflected portions. In some embodiments, the plurality of axes ofreflection is the same as the second plurality of axes of reflection. Insome embodiments, the plurality of axes of reflection is different fromthe second plurality of axes of reflection.

At block 1544, in response to detecting the user input corresponding toa selection of the second preview image, the first device optionallyreplaces the second composite image with a third composite imagecomprising the third plurality of reflected portions (see background1462 c on display 1452 in FIG. 14E). In some embodiments, in response todetecting the user input corresponding to a selection of the secondpreview image, the second electronic device sends data to the firstdevice comprising instructions to replace the second composite imagewith a third composite image comprising the third plurality of reflectedportions.

At block 1546, the second electronic device optionally displays (e.g.,as part of the second user interface screen) a preview imagerepresenting the first user interface screen on the first electronicdevice (e.g., representation 1404 in FIG. 14D). In some embodiments, thepreview image comprises a representation of the second composite image.

In FIG. 15D, at block 1548, the second electronic device optionallyupdates the preview image by replacing the representation of the secondcomposite image with a representation of the third composite image (cf.representation 1404 in FIG. 14D and FIG. 14E) in response to detectingthe user input corresponding to a selection of the second preview image.

At block 1550, the second electronic device optionally displays (e.g.,as part of the second user interface screen) an affordance representinga pattern of axes of reflection (e.g., representations 1412, 1414, and1416 on display 1402 in FIG. 14B).

At block 1552, the second electronic device optionally detects a userinput corresponding to a selection of the affordance representing thepattern of axes of reflection (e.g., tap 1420 in FIG. 14B).

At block 1554, in response to detecting the user input corresponding toa selection of the affordance, the first or second electronic deviceoptionally reflects the portion of the second image across a secondplurality of axes of reflection to generate a fourth plurality ofreflected portions. In some embodiments, the fourth plurality ofreflected portions is different from the third plurality of reflectedportions.

At block 1556, in response to detecting the user input corresponding toa selection of the affordance, the first device replaces the thirdcomposite image with a fourth composite image comprising the fourthplurality of reflected portions (e.g., background 1462 b in FIG. 14C).In some embodiments, the second electronic device optionally updates thepreview image by replacing the representation of the second compositeimage with a representation of the fourth composite image (cf.representation 1404 in FIG. 14B and FIG. 14C) in response to detectingthe user input corresponding to a selection of the affordance. In someembodiments, in response to detecting the user input corresponding to aselection of the affordance, the second electronic device sends data tothe first device comprising instructions to replace the third compositeimage with a fourth composite image comprising the fourth plurality ofreflected portions.

At block 1558, the device optionally displays an affordance thatrepresents an application (e.g., complication 1108 in FIG. 11E). Asshown in block 1560, in some embodiments, the affordance comprises a setof information obtained from the application it represents.

In FIG. 15E, at block 1562, the device optionally detects a user inputcorresponding to a selection of the affordance (e.g., tap 1120 in FIG.11E).

At block 1564, the device optionally launches the applicationrepresented by the affordance in response to detecting the user inputcorresponding to a selection of the affordance (see FIG. 11F). In someembodiments, launching the application represented by the affordancecomprises ceasing to display the first user interface screen anddisplaying a third user interface screen corresponding to theapplication represented by the affordance.

At block 1566, the device optionally receives data from the applicationrepresented by the affordance.

At block 1568, the device optionally updates the set of informationdisplayed by the affordance in accordance with the received data (seecomplication 1108 in FIGS. 11A-11C, or complication 1110 in FIGS.11A-11C). In some embodiments, the affordance is displayed in the sameposition on the display before and after updating the set ofinformation. Thus, the affordance is able to display updated informationfrom an application without requiring the user to launch the applicationto view the updated information. Performing an operation when a set ofconditions has been met without requiring further user input enhancesthe operability of the device and makes the user-device interface moreefficient (e.g., by helping the user to provide proper inputs andreducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

At block 1570, the device optionally detects a contact (e.g., on thetouch sensitive display; see tap 1122 in FIG. 11G). In some embodiments,the contact is at the displayed second composite image.

At block 1572, the device optionally displays the image (e.g., byreplacing the second composite image with the image; see image 1124 inFIG. 11H).

Note that details of the processes described above with respect toprocess 1500 (e.g., FIGS. 15A-15E) are also applicable in an analogousmanner to the methods described elsewhere in this application. Forexample, other methods described in this application may include one ormore of the characteristics of process 1500. For example, one or more ofthe steps of process 1500 can be combined with one or more of the stepsof process 1600, as described below. For brevity, these details are notrepeated below.

FIGS. 16A-16D show a flow diagram illustrating process 1600 forproviding context-specific user interfaces. In some embodiments, process1600 can be performed at an electronic device with a touch-sensitivedisplay, one or more processors, and memory, such as device 100 (FIG.1A), 300 (FIG. 3 ), 500 (FIGS. 5A-5H), or 1100 (FIGS. 11A-11N). Someoperations in process 1600 can be combined, the order of some operationsmay be changed, and some operations can be omitted.

In FIG. 16A, at block 1602, the device optionally displays a userinterface screen comprising a current time indicator (e.g., 1104 in FIG.11A) and a first composite image (e.g., similar to 1158 in FIG. 11M).The image is created by the electronic device (e.g., automatically) byselecting a first portion of an image (block 1604), reflecting the firstportion across a first plurality of axes of reflection to generate afirst plurality of reflected portions (block 1606), and displaying thefirst plurality of reflected portions (block 1608).

At block 1610, the device detects a user input corresponding to arequest to edit the first composite image.

At block 1612, in response to detecting the user input, the deviceceases to display the first composite image.

At block 1614, in response to detecting the user input, the devicedisplays a second composite image (e.g., similar to 1166 in FIG. 11N).The image is created by the electronic device (e.g., automatically) byselecting a second portion of the image (block 1616), reflecting thesecond portion across a second plurality of axes of reflection togenerate a second plurality of reflected portions (block 1618), anddisplaying the second plurality of reflected portions (block 1620). Insome embodiments, the first and the second plurality of axes ofreflection are different (e.g., based on different patterns).Automatically selecting the portion of the image using the deviceenhances the variety of backgrounds that can be displayed by the devicewithout requiring the user to select a portion each time the imagechanges. Performing an operation when a set of conditions has been metwithout requiring further user input enhances the operability of thedevice and makes the user-device interface more efficient (e.g., byhelping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In FIG. 16B, at block 1622, the device optionally detects a user inputcorresponding to a request to enter a composite image edit mode of theelectronic device (e.g., press 1130 in FIG. 11I). In some embodiments,the user input is a press having a duration longer than a predeterminedduration (e.g., a “long press” input). In some embodiments, the devicedetermines whether the detected press has a duration longer than apredetermined duration and, in accordance with a determination that thedetected press has a duration longer than the predetermined duration,enters the affordance edit mode. In some embodiments, the user input isa contact having a characteristic intensity above an intensitythreshold. In some embodiments, the device determines whether thedetected contact has a characteristic intensity above a predeterminedduration and, in accordance with a determination that the detected presshas a characteristic intensity above the predetermined duration, entersthe affordance edit mode.

At block 1624, the device optionally enters a composite image edit modein response to detecting the user input corresponding to a request toenter composite image edit mode. In some embodiments, as shown at block1626, entering the composite image edit mode comprises displaying anedit mode affordance on the touch-sensitive display (e.g., affordance1134 in FIG. 11J) and, as shown at block 1628, detecting a user inputcorresponding to a selection of the edit mode affordance (e.g., tap 1140in FIG. 11J).

At block 1630, the device optionally visually distinguishes thecomposite image to indicate the composite image edit mode in response todetecting the user input corresponding to a request to enter compositeimage edit mode. For example, the device can display an outline aroundthe affordance, animate an outline around the affordance, animate theaffordance (e.g., to flash or expand and contact) change a color of theaffordance, and/or display an additional indicator to visuallydistinguish the affordance (see outline 1140 in FIG. 11K). Visuallydistinguishing the composite image to indicate edit mode providesimproved feedback to the user both that the device has entered adifferent mode of functionality (for example, tapping the compositeimage can lead to display of the original image during a mode other thanedit mode but select the composite image for editing during edit mode)and that the distinguished composite image is the aspect of theinterface currently selected for editing. Providing improved feedbackenhances the operability of the device and makes the user-deviceinterface more efficient (e.g., by helping the user to provide properinputs and reducing user mistakes when operating/interacting with thedevice) which, additionally, reduces power usage and improves batterylife of the device by enabling the user to use the device more quicklyand efficiently. In some embodiments, as shown at block 1632, visuallydistinguishing the composite image to indicate the composite image editmode further comprises displaying an indicator of position along aseries of positions, the indicator indicating a first position along theseries (e.g., scroll indicator 1160 a in FIG. 11M). In some embodiments,as shown at block 1634, the device updates the indicator of position toindicate a second position along the series, where the indicator ofposition along a series of positions indicates a position of a currentlyselected option for the composite image pattern along a series ofselectable options for the composite image (see scroll indicator 1160 bin FIG. 11N). Displaying an updating scroll indicator that indicates aposition of a currently displayed composite image pattern along a seriesof selectable patterns provides feedback to the user that the receiveduser input (e.g., scroll 1162 in FIG. 11M) controls selection of thecomposite image generation pattern while helping the user to navigatethrough the entire series of patterns (as well as indicating to the userthat additional patterns are selectable). Providing improved feedbackenhances the operability of the device and makes the user-deviceinterface more efficient (e.g., by helping the user to provide properinputs and reducing user mistakes when operating/interacting with thedevice) which, additionally, reduces power usage and improves batterylife of the device by enabling the user to use the device more quicklyand efficiently.

At block 1636, the device optionally detects a user input correspondingto a request to select an image (e.g., after visually distinguishing thedisplayed composite image to indicate an image selection mode). Forexample, in some embodiments, detecting the user input corresponding toa request to select an image comprises detecting a swipe on the display(e.g., swipe 1148 or 1156 in FIGS. 11K & 11L).

In FIG. 16C, at block 1638, the device optionally ceases to display thesecond plurality of reflected portions in response to detecting the userinput corresponding to a request to select an image.

At block 1640, the device optionally selects a first portion of a secondimage different from the first image (e.g., automatically by the device)in response to detecting the user input corresponding to a request toselect an image.

At block 1642, the device optionally reflects the first portion of thesecond image across a plurality of axes of reflection to generate athird plurality of reflected portions in response to detecting the userinput corresponding to a request to select an image.

At block 1644, the device optionally displays a third composite imagecomprising the third plurality of reflected portions in response todetecting the user input corresponding to a request to select an image(e.g., background 1166 in FIG. 11N).

At block 1646, the device optionally displays an affordance thatrepresents an application (e.g., complication 1108 in FIG. 11E). Asshown in block 1648, in some embodiments, the affordance comprises a setof information obtained from the application it represents.

At block 1650, the device optionally detects a user input correspondingto a selection of the affordance (e.g., tap 1120 in FIG. 11E).

In FIG. 16D, at block 1652, the device optionally launches theapplication represented by the affordance. In some embodiments,launching the application comprises ceasing to display the first userinterface screen and displaying a user interface screen corresponding tothe application (see FIG. 11F).

At block 1654, the device optionally receives data from the applicationrepresented by the affordance.

At block 1656, the device optionally updates the set of informationdisplayed by the affordance in accordance with the received data (cf.complication 1108 in FIGS. 11A-11C). In some embodiments, the affordanceis displayed in the same position on the display before and afterupdating the set of information.

At block 1658, the device detects a swipe, e.g., after visuallydistinguishing the displayed composite image to indicate the compositeimage edit mode (e.g., swipe 1148 in FIG. 11K).

At block 1660, the device optionally visually distinguishes thedisplayed affordance to indicate an affordance edit mode. For example,the device can display an outline around the affordance, animate anoutline around the affordance, animate the affordance (e.g., to flash orexpand and contact) change a color of the affordance, and/or display anadditional indicator to visually distinguish the affordance (see outline1150 and indicator 1154 in FIG. 11L). Visually distinguishing theaffordance to indicate edit mode provides improved feedback to the userboth that the device has entered a different mode of functionality (forexample, tapping the affordance can lead to launching the applicationduring a mode other than edit mode but select the affordance for editingduring edit mode) and that the distinguished affordance is the aspect ofthe interface currently selected for editing. Providing improvedfeedback enhances the operability of the device and makes theuser-device interface more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

At block 1662, the device optionally detects a user input correspondingto a request to edit the affordance (e.g., scroll 682 in FIG. 6U).

At block 1664, the device optionally updates the affordance to representa second application in response to detecting the user inputcorresponding to a request to edit the affordance (e.g., complication684 in FIG. 6V). In some embodiments, the affordance comprises a secondset of information obtained from the second application. In someembodiments, the second set of information is updated in accordance withdata from the second application. In some embodiments, the first and thesecond applications are different (e.g., personal assistant vs. remoteapplication in FIGS. 6U-6V).

At block 1666, the device optionally updates the affordance to comprisea second set of information obtained from the application in response todetecting the user input corresponding to a request to edit theaffordance. In some embodiments, the second set of information isupdated in accordance with data from the application. In someembodiments, the first and the second sets of information are different.Thus, the user can edit the set of application information that isdisplayed from multiple options (e.g., multiple time zones from a worldclock application, or multiple stock prices from a stocks application).

Note that details of the processes described above with respect toprocess 1600 (e.g., FIGS. 16A-16D) are also applicable in an analogousmanner to the methods described elsewhere in this application. Forexample, other methods described in this application may include one ormore of the characteristics of process 1600. For example, one or more ofthe steps of process 1600 can be combined with one or more of the stepsof process 1500, as described above. For brevity, these details are notrepeated below.

In any of the embodiments described herein, the device (e.g., 500, 600,900, 1100, 1210, 1320, and/or 1450) can be a portable or reduced-sizemultifunction device (e.g., a smart watch electronic device) with one ormore attachment mechanisms. FIGS. 17A & 17B show exemplary device 1700.Device 1700 may be device 100, 300, 500, 600, 900, 1100, 1210, 1320, or1450 in some embodiments. The electronic device has a display 1702(e.g., 504). In some embodiments, display 1702 is a touch-sensitivedisplay. In some embodiments, device 1700 includes a rotatable inputmechanism and/or input mechanism or button.

FIGS. 17A & 17B illustrate that device 1700 can detect a user movementof the device and, in response to detecting the user movement, display auser interface screen (e.g., described herein). In some embodiments, theuser movement can be a raising and/or rotation of the user's wrist, orother movement indicative of the user raising the display into viewingposition. These movements could be detected, for example, by using anaccelerometer (e.g., 534), a gyroscope (e.g., 536), a motion sensor(e.g., 538), and/or a combination thereof. In any of thecontext-dependent faces described herein, a movement of the device maybe a user input that activates the display.

In FIG. 17A, the display of device 1700 is powered off. In FIG. 17B, inresponse to detecting a raising and/or rotation of the user's wrist,device 1700 powers on the display and displays a user interface screen.For any of the user interface screens described above, the display canbe powered off prior to displaying the user interface screen, and thedevice can power on the display and display the user interface screen inresponse to detecting the a user movement of the device.

FIG. 18 shows a flow diagram illustrating process 1800 for displayingcontext-specific user interfaces. In some embodiments, process 1800 canbe performed at an electronic device with a touch-sensitive display, oneor more processors, and memory, such as device 100 (FIG. 1A), 300 (FIG.3 ), 500 (FIGS. 5A-5H), 600 (FIGS. 6A-6V), 900 (FIGS. 9A-9L), 1100(FIGS. 11A-11N), 1450 (FIGS. 14B-14E), or 1900 (FIGS. 19A-19F). Someoperations in process 1800 can be combined, the order of some operationsmay be changed, and some operations can be omitted.

In FIG. 18 , at block 1802, the device powers off the display (e.g.,display 1702 in FIG. 17A).

At block 1804, device 1700 detects a user movement of the device (e.g.,raising and/or rotation of the wrist; cf. FIGS. 17A & 17B).

At block 1806, the device powers on the display in response to detectingthe user movement of the device (e.g., display 1702 in FIG. 17B).

At block 1808, the device displays a user interface screen (e.g., asdescribed above) in response to detecting the user movement of thedevice (e.g., display 1702 in FIG. 17B). Thus, the device can display auser interface screen automatically when the user raises the device intoviewing position, rather than requiring an additional user input topower on the display when the user is viewing it. Reducing the number ofinputs needed to perform an operation enhances the operability of thedevice and makes the user-device interface more efficient (e.g., byhelping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

Note that details of the processes described above with respect toprocess 1800 (e.g., FIG. 18 ) are also applicable in an analogous mannerto the methods described elsewhere in this application. For example,other methods described in this application may include one or more ofthe characteristics of process 1800. For example, one or more steps ofprocess 1800 can occur prior to block 702 of process 700, block 802 ofprocess 800, block 1002 of process 1000, block 1502 of process 1500, orblock 1602 of process 1600, as described above. For brevity, thesedetails are not repeated below.

Turning now to FIG. 19A, a user may wish for character-based userinterface objects with a more natural and lifelike appearance and/orincreased interactability with the user. Further, a user may wish forthe character-based user interface object to act in a more dynamicmanner, to interact with the user, and/or to provide event-relatedinformation to a user. Described below are context-specific userinterfaces with increased interactability. Any of the techniquesdescribed below can be combined with the techniques described inInternational Patent Application Serial No. PCT/US2015/034604, titled“Context-Specific User Interfaces,” filed Jun. 7, 2015, published asWIPO Publication No. WO/2016/022203, e.g., in reference to characteruser interface objects. The features described herein allow a characteruser interface object to appear more natural and lifelike by adopting awider range of natural motions while indicating a time. A user may wishto view representations of other events by the character user interfaceobject. Allowing the character user interface object to react toexternal stimuli or internal system events portrays a more interactivecharacter, thus depicting a closer representation of a personality. Theenhanced interactivity of the character further improves the user'sinteractions with the device by providing additional notification thatan event has occurred, the occurrence of which may not have been asapparent otherwise. A character user interface object may serve tosupply notifications, reminders, and/or other information a user maywish to access from a personal electronic device, but the use of acharacter provides an interactive personality that the device may use tosupply these items. Further, making the character responsive to internalsystem events (e.g., calendar events and the like) means the characteris not strictly limited to responding to external user input. Putanother way, the character appears to have a more lifelike personalitybecause it responds to events not directly prompted by the immediateactions of the user.

FIGS. 19A-19F show exemplary context-specific user interfaces that maybe operated on device 1900. Device 1900 may be device 100, 300, or 500in some embodiments. The electronic device has a display 1902 (e.g.,504). In some embodiments, display 1902 is a touch-sensitive display. Insome embodiments, device 1100 includes a rotatable input mechanism 1910a (e.g., 506) and/or input mechanism or button 1910 b (e.g., 508).

In FIG. 19A, device 1900 displays a user interface screen that includescomplications 1904, 1906, and 1908, current time indicator 1904, andcharacter user interface object 1902 a. A character user interfaceobject can include any representation of a character, for example ahuman or anthropomorphized character. In some embodiments, a charactercan be a cartoon figure. In some embodiments, one or more soundscorresponding to the character user interface object (e.g., speech orsound associated with the character) are played (e.g., using a speaker).

In FIG. 19A, device 1900 animates character user interface object 1902a/1902 b to walk from off-screen onto the middle of display 1902 andstop. In some embodiments, the animation is displayed in response todetecting a user input, e.g., powering on the device or detecting a usermovement of device 1900.

In FIG. 19B, device 1900 animates character user interface object 1902 cto react to a displayed user interface object. In this example,character user interface object 1902 c reacts to the display ofnotifications dot 1912, which indicates to the user that one or morenotifications (e.g., unread notifications) have been received, such as amissed call, email, voicemail, text message, and the like. In someembodiments, character user interface object 1902 c is animated tointeract with one or more displayed user interface objects such as acomplication (e.g., 1904, 1906, or 1908, such as by climbing on ortripping over the displayed text).

In some embodiments, character user interface object 1902 c is animatedto interact with the current time indicator (FIG. 19C). In FIG. 19C,character user interface object 1902 d points at indicator 1914 a, e.g.,at a change in time. After the animation, indicator 1914 b is updated,e.g., as if changed by or reacting to character user interface object1902 d.

In other embodiments, character user interface object 1902 e reacts totime indicator 1914 b, e.g., by removing his hat. For example, characteruser interface object 1902 e can react to a certain time of day (e.g.,not an even hour or half-hour) or certain date, e.g., a time or date ofsignificance to the character (e.g., an “Easter egg”). This increasesuser interactions with the device, e.g., by promoting the user tointeract with the device at different times to discover an “Easter egg.”In some embodiments, device 1900 detects a user touch gesture (e.g.,tap) on display 1902), and in response to detecting the touch gesture,device 1900 animates the character user interface object to react to thetouch.

In some embodiments, character user interface object 1902 f reacts tothe displayed information of a complication. For example, in FIG. 19D,character user interface object 1902 f takes off his hat and swipes hisbrow because the current weather conditions are warm (as indicated bythe information displayed by complication 1908 b). This reinforces theinformation displayed by the complication (e.g., as obtained from thecorresponding application).

In some embodiments, multiple animated sequences for the character userinterface object can be displayed. For example, one animated sequence isshown in FIG. 19A. In FIG. 19E, device 1900 animates character userinterface object 1902 g/1902 h to parachute on-screen onto the middle ofdisplay 1902 and stop. In some embodiments, the animation is displayedin response to detecting a user input, e.g., powering on the device ordetecting a user movement of device 1900. In some embodiments, one ormore animated sequences for the character user interface object can bedisplayed in response to detecting a user interaction, such as a touchgesture on the display.

In some embodiments, multiple character user interface objects can beselected for display at device 1900. The user may wish to select adifferent character user interface object. Any of the editing andselection techniques described herein or in International PatentApplication Serial No. PCT/US2015/034607, titled “Context-Specific UserInterfaces,” filed Jun. 7, 2015, published as WIPO Publication No.WO/2016/022205, can be used.

In FIG. 19F, the user accesses an edit mode of device 1900 through press1922, which in some embodiments can be a press having a duration longerthan a predetermined duration (e.g., a “long press” input) or a contacthaving a characteristic intensity above an intensity threshold. In thisexample, in response to detecting press 1922, device 1900 enters acontext-specific user interface selection mode and visuallydistinguishes the user interface screen to indicate the selection mode.Device 1900 alerts to the user that it has entered into the selectionmode by displaying smaller representation 1924 of the user interfacescreen, name 1928 corresponding to a name of the type ofcontext-specific user interface currently selected, partial view 1930 ofan adjacent, stored context-specific user interface (which the usercould select by swiping to view the full interface and tapping to selectit), and edit affordance 1926. In order to edit the character userinterface object, the user contacts edit affordance 1926 via tap 1932.

In response to detecting tap 1932, the device enters edit mode andvisually distinguishes one or more aspects of the user interface forediting. In this example, character user interface object 1902 i isselected for editing (e.g., selecting a character). Device 1900 informsthe user that user interface object 1902 i is selected for editing byvisually distinguishing user interface object 1902 i via displayingoutline 1932 a around user interface object 1902 i and indicator 1932 b,which indicates that the character is editable. Device 1900 alsodisplays scroll indicator 1936, which informs the user that additionalcharacters can be selected by scrolling and indicates the position ofthe character along the series of displayable characters. Device 1900also displays paging affordance 1934, which indicates that three optionsfor editing different aspects of the user interface can be selected(e.g., by swiping). In this example, the options include the character,the application associated with various complications, and one or morecolors (e.g., a color associated with the character user interfaceobject and/or an additional display element).

To edit a different aspect of the interface, the user swipes display1902, e.g., via swipe. To change the character, the user rotates 1910 avia scroll 1938. In response to detecting scroll 1938, device 1900ceases to display 1902 i and displays character user interface object1940 (FIG. 19F). Indicator 1932 b is also updated to reflect thecharacter. Scroll indicator 1942 is also updated to indicate theposition of the new character along the series of selectable characters.In some embodiments, the user can then exit edit mode and display theedited user interface screen. In some embodiments, upon exiting editmode, the device saves the edited user interface screen in memory, e.g.,such that it can be subsequently selected in selection mode, e.g., asdescribed in International Patent Application Serial No.PCT/US2015/034607, titled “Context-Specific User Interfaces,” filed Jun.7, 2015, published as WIPO Publication No. WO/2016/022205 (see, e.g.,display 1322 in FIG. 13 ).

In any of the embodiments described herein, or any of the embodimentsdescribed in International Patent Application Serial No.PCT/US2015/034604, titled “Context-Specific User Interfaces,” filed Jun.7, 2015, published as WIPO Publication No. WO/2016/022203, acontext-specific user interface displays one or more colors indicativeof wireless communication functionality. For example, a context-specificuser interface can include a color only for devices capable of long termevolution (LTE) wireless communication. In some embodiments, acontext-specific user interface displays one or more user interfaceobjects that indicate wireless connectivity status. For example, one ormore dots can be displayed, where a larger number of dots indicateshigher signal strength. In some embodiments, a color of the one or moredots indicates the type of wireless communication that the device iscurrently using (e.g., one color for LTE and another color for WiFi). Insome embodiments, the one or more dots can be an affordance that theuser can select (e.g., by tapping). In response to detecting the userselection (e.g., tap), the device displays a user interface screen forchanging a wireless communication setting (e.g., turning off/on LTE orWiFi).

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the scope of the disclosure to the precise forms disclosed. Manymodifications and variations are possible in view of the aboveteachings. The embodiments were chosen and described in order to bestexplain the principles of the techniques and their practicalapplications. Others skilled in the art are thereby enabled to bestutilize the techniques and various embodiments with variousmodifications as are suited to the particular use contemplated.

Although the disclosure and examples have been fully described withreference to the accompanying figures, it is to be noted that variouschanges and modifications will become apparent to those skilled in theart. Such changes and modifications are to be understood as beingincluded within the scope of the disclosure and examples as defined bythe appended claims.

What is claimed is:
 1. An electronic device, comprising: a display; oneor more processors; and memory storing one or more programs configuredto be executed by the one or more processors, the one or more programsincluding instructions for: at a first time of a current day, displayingon the display a first user interface screen comprising: a current timeindicator, wherein the current time indicator reflects the first time ofthe current day; a first platter at a first position on the display,wherein the first platter is associated with a first application anddisplays a first set of information obtained from the first application,wherein the first set of information relates to a first temporal contextof the current day; and an affordance at a second position on thedisplay, wherein the affordance represents an application; detecting afirst user input corresponding to a request to scroll the first userinterface screen; in response to detecting the first user input,displaying a second platter at the first position, wherein the secondplatter is associated with a second application and displays a secondset of information obtained from the second application, wherein thesecond set of information relates to the current day, and wherein afirst side of the second platter is displayed adjacent to a platter withinformation that relates to the first temporal context of the currentday; at a second time of the current day different from the first time,displaying on the display a second user interface screen comprising: thecurrent time indicator, wherein the current time indicator reflects thesecond time of the current day; a third platter at the first position onthe display, wherein the third platter is associated with a thirdapplication and displays a third set of information obtained from thethird application, wherein the third set of information relates to athird temporal context of the current day; and the affordance at thesecond position on the display; detecting a second user inputcorresponding to a request to scroll the second user interface screen;and in response to detecting the second user input, displaying thesecond platter at the first position, wherein the first side of thesecond platter is displayed adjacent to a platter with information thatrelates to the third temporal context of the current day.
 2. Theelectronic device of claim 1, wherein the second user input correspondsto a request to scroll the second user interface screen in a firstscroll direction, the one or more programs further includinginstructions for: at the second time of day, detecting a third userinput corresponding to a request to scroll the second user interfacescreen in a second scroll direction different from the first scrolldirection; and in response to detecting the third user input: displayinga fourth platter at the first position on the display, wherein thefourth platter is associated with a fourth application and displays afourth set of information obtained from the fourth application, whereinthe fourth set of information relates to a fourth temporal context ofthe current day, and wherein the fourth temporal context is differentfrom the third temporal context.
 3. The electronic device of claim 2,wherein the fourth temporal context is later than the third temporalcontext in the current day.
 4. The electronic device of claim 2, the oneor more programs further including instructions for: in response todetecting the second user input: displaying on the display an indicatorof position along a series of positions, wherein the indicator ofposition along a series of positions indicates a position of the secondplatter along a series of displayable platters; and in response todetecting the third user input: updating the indicator of position toindicate a position of the fourth platter along the series ofdisplayable platters.
 5. The electronic device of claim 2, the one ormore programs further including instructions for: at the second time ofday, detecting a fourth user input corresponding to a request to scrollthe second user interface screen in the second scroll direction; and inresponse to detecting the fourth user input: displaying a fifth platterat the first position on the display, wherein the fifth platter isassociated with a fifth application and displays a fifth set ofinformation obtained from the fifth application, wherein the fifth setof information relates to a temporal context of a next day.
 6. Theelectronic device of claim 2, the one or more programs further includinginstructions for: at the second time of day, and after displaying thefourth platter, detecting a fifth user input; and in response todetecting the fifth user input: ceasing to display the fourth platter;and displaying the third platter at the first position.
 7. Theelectronic device of claim 6, wherein the electronic device furthercomprises a rotatable input mechanism, and wherein the fifth user inputcomprises a rotation of the rotatable input mechanism.
 8. The electronicdevice of claim 6, wherein the display is a touch-sensitive display, andwherein the fifth user input comprises a contact on the touch-sensitivedisplay.
 9. The electronic device of claim 1, wherein the electronicdevice further comprises a rotatable input mechanism, and wherein thefirst user input comprises a rotation of the rotatable input mechanism.10. The electronic device of claim 2, wherein the electronic devicefurther comprises a rotatable input mechanism, wherein the second userinput comprises a rotation of the rotatable input mechanism in a firstdirection of rotation, and wherein the third user input comprises arotation of the rotatable input mechanism in a second direction ofrotation different from the first direction of rotation.
 11. Theelectronic device of claim 1, wherein the display is a touch-sensitivedisplay, and wherein the first user input comprises a swipe on thetouch-sensitive display.
 12. The electronic device of claim 2, whereinthe display is a touch-sensitive display, wherein the second user inputcomprises a swipe on the touch-sensitive display in a first swipedirection, and wherein the third user input comprises a swipe on thetouch-sensitive display in a second swipe direction different from thefirst swipe direction.
 13. The electronic device of claim 1, wherein thefirst and the third sets of information are selected for display basedat least in part on a set of one or more selection criteria.
 14. Theelectronic device of claim 13, wherein the set of one or more selectioncriteria comprises a temporal context of the current day.
 15. Theelectronic device of claim 14, wherein the set of one or more selectioncriteria comprises a temporal context of the current day and one or moreselection criteria selected from the group consisting of: location, theapplication from which the first or the third set of information isobtained, a number of calendar events scheduled for the current day,time until the next scheduled calendar event, and one or more previoususer inputs.
 16. The electronic device of claim 15, wherein the set ofone or more selection criteria comprises a temporal context of thecurrent day and location, the one or more programs further includinginstructions for: before displaying the first user interface screen,obtaining a current location of the electronic device from a locationsensor associated with the electronic device, wherein the set of one ormore selection criteria comprises proximity to the current location ofthe electronic device.
 17. The electronic device of claim 1, wherein thesecond set of information is selected for display based at least in parton a second set of one or more selection criteria.
 18. The electronicdevice of claim 17, wherein the second set of one or more selectioncriteria comprises location.
 19. The electronic device of claim 18, theone or more programs further including instructions for: beforedisplaying the first user interface screen, obtaining a current locationof the electronic device from a location sensor associated with theelectronic device, and wherein the second set of one or more selectioncriteria comprises proximity to the current location of the electronicdevice.
 20. The electronic device of claim 17, wherein the second set ofone or more selection criteria comprises the application from which thesecond set of information is obtained.
 21. The electronic device ofclaim 17, wherein the second set of one or more selection criteria doesnot comprise a temporal context of the current day.
 22. The electronicdevice of claim 17, wherein the second set of information relates to amajority of time within the current day.
 23. The electronic device ofclaim 17, wherein the second set of information relates to a temporalcontext of the current day that is broader than the first and the thirdtemporal contexts.
 24. The electronic device of claim 1, the one or moreprograms further including instructions for: while displaying the secondplatter, detecting a user input corresponding to a selection of thesecond platter; and in response to detecting the user inputcorresponding to a selection of the second platter: launching the secondapplication.
 25. The electronic device of claim 24, wherein launchingthe second application comprises ceasing to display the first or seconduser interface screen and displaying a third user interface screen,wherein the third user interface screen corresponds to the secondapplication.
 26. The electronic device of claim 24, wherein the displayis a touch-sensitive display, and wherein detecting the user inputcorresponding to the selection of the second platter comprises detectinga contact on the touch-sensitive display at the displayed secondplatter.
 27. The electronic device of claim 1, the one or more programsfurther including instructions for: detecting a user input correspondingto a selection of the affordance; and in response to detecting the userinput corresponding to a selection of the affordance: launching theapplication represented by the affordance.
 28. The electronic device ofclaim 27, wherein launching the application represented by theaffordance comprises ceasing to display the first or second userinterface screen and displaying a fourth user interface screen, whereinthe fourth user interface screen corresponds to the applicationrepresented by the affordance.
 29. The electronic device of claim 27,wherein the display is a touch-sensitive display, and wherein detectingthe user input corresponding to the selection of the affordancecomprises detecting a contact on the touch-sensitive display at thedisplayed affordance.
 30. The electronic device of claim 1, the one ormore programs further including instructions for: detecting a user inputcorresponding to a request to enter an affordance edit mode of theelectronic device; and in response to detecting the user inputcorresponding to the request to enter affordance edit mode: entering anaffordance edit mode of the electronic device; visually distinguishingthe affordance to indicate the affordance edit mode; detecting a thirduser input corresponding to a request to change the applicationrepresented by the affordance; and in response to detecting the thirduser input corresponding to the request to change the application:updating the affordance to represent a different application.
 31. Theelectronic device of claim 30, wherein the display is a touch-sensitivedisplay, and wherein entering the affordance edit mode comprises:displaying an edit mode affordance on the touch-sensitive display; anddetecting a user input corresponding to a selection of the edit modeaffordance; wherein the affordance is visually distinguished in responseto detecting the user input corresponding to the selection of the editmode affordance.
 32. The electronic device of claim 31, wherein thedisplay is a touch-sensitive display, and wherein detecting the userinput corresponding to the selection of the edit mode affordancecomprises detecting a contact on the touch-sensitive display at thedisplayed edit mode affordance.
 33. The electronic device of claim 30,wherein the electronic device further comprises a rotatable inputmechanism, and wherein detecting the third user input comprisesdetecting a rotation of the rotatable input mechanism.
 34. Theelectronic device of claim 33, wherein visually distinguishing theaffordance to indicate the affordance edit mode further comprisesdisplaying an indicator of position along a series of positions, theindicator indicating a first position along the series; the one or moreprograms further including instructions for: in response to detectingthe third user input: updating the indicator of position to indicate asecond position along the series, wherein the indicator of positionalong a series of positions indicates a position of a currently selectedoption for the application represented by the affordance along a seriesof selectable options for the application represented by the affordance.35. The electronic device of claim 1, wherein the first and the secondapplications are the same.
 36. The electronic device of claim 1, whereinthe first and the second applications are the different.
 37. Theelectronic device of claim 1, wherein the first and the thirdapplications are the same.
 38. The electronic device of claim 1, whereinthe first and the third applications are the different.
 39. Theelectronic device of claim 1, wherein the electronic device is a smartwatch electronic device comprising one or more attachment mechanisms,the one or more programs further including instructions for: beforedisplaying the first user interface screen, detecting a user movement ofthe smart watch electronic device; and in response to detecting the usermovement: displaying the first user interface screen.
 40. The electronicdevice of claim 39, wherein the user movement comprises a raising of awrist of the user.
 41. The electronic device of claim 39, wherein thedisplay is powered off prior to detecting the user movement, and whereinthe display is powered on in response to detecting the user movement.42. A non-transitory computer-readable storage medium storing one ormore programs configured to be executed by one or more processors of anelectronic device with a display, the one or more programs includinginstructions for: at a first time of a current day, displaying on thedisplay a first user interface screen comprising: a current timeindicator, wherein the current time indicator reflects the first time ofthe current day; a first platter at a first position on the display,wherein the first platter is associated with a first application anddisplays a first set of information obtained from the first application,wherein the first set of information relates to a first temporal contextof the current day; and an affordance at a second position on thedisplay, wherein the affordance represents an application; detecting afirst user input corresponding to a request to scroll the first userinterface screen; in response to detecting the first user input,displaying a second platter at the first position, wherein the secondplatter is associated with a second application and displays a secondset of information obtained from the second application, wherein thesecond set of information relates to the current day, and wherein afirst side of the second platter is displayed adjacent to a platter withinformation that relates to the first temporal context of the currentday; at a second time of the current day different from the first time,displaying on the display a second user interface screen comprising: thecurrent time indicator, wherein the current time indicator reflects thesecond time of the current day; a third platter at the first position onthe display, wherein the third platter is associated with a thirdapplication and displays a third set of information obtained from thethird application, wherein the third set of information relates to athird temporal context of the current day; and the affordance at thesecond position on the display; detecting a second user inputcorresponding to a request to scroll the second user interface screen;and in response to detecting the second user input, displaying thesecond platter at the first position, wherein the first side of thesecond platter is displayed adjacent to a platter with information thatrelates to the third temporal context of the current day.
 43. A method,comprising: at an electronic device with a display, one or moreprocessors, and memory: at a first time of a current day, displaying onthe display a first user interface screen comprising: a current timeindicator, wherein the current time indicator reflects the first time ofthe current day; a first platter at a first position on the display,wherein the first platter is associated with a first application anddisplays a first set of information obtained from the first application,wherein the first set of information relates to a first temporal contextof the current day; and an affordance at a second position on thedisplay, wherein the affordance represents an application; detecting afirst user input corresponding to a request to scroll the first userinterface screen; in response to detecting the first user input,displaying a second platter at the first position, wherein the secondplatter is associated with a second application and displays a secondset of information obtained from the second application, wherein thesecond set of information relates to the current day, and wherein afirst side of the second platter is displayed adjacent to a platter withinformation that relates to the first temporal context of the currentday; at a second time of the current day different from the first time,displaying on the display a second user interface screen comprising: thecurrent time indicator, wherein the current time indicator reflects thesecond time of the current day; a third platter at the first position onthe display, wherein the third platter is associated with a thirdapplication and displays a third set of information obtained from thethird application, wherein the third set of information relates to athird temporal context of the current day; and the affordance at thesecond position on the display; detecting a second user inputcorresponding to a request to scroll the second user interface screen;and in response to detecting the second user input, displaying thesecond platter at the first position, wherein the first side of thesecond platter is displayed adjacent to a platter with information thatrelates to the third temporal context of the current day.